Reconstruction of an optical network link in a link viewer based on a text file

ABSTRACT

A device may be configured to receive a text file including network information for an optical network. The network information may include information for an optical route in the optical network. The device may generate a user interface based on the text file. The user interface may display a representation of the optical route. The device may provide the user interface for display and receive a user input via the user interface. The device may change the representation of the optical route displayed by the user interface based on the user input and the network information included in the text file.

BACKGROUND

In optical networks, signals may be transmitted at various wavelengths,with each wavelength corresponding to a transmission channel. Opticallinks may connect network nodes so that signals may be transmittedthroughout the optical network. An optical route may use a series ofnetwork nodes and optical links to connect a source of an opticaltransmission with a destination for the optical transmission.

SUMMARY

According to some possible implementations, a device may include atleast one processor and receive a text file including networkinformation for an optical network. The network information may includeinformation for an optical route in the optical network. The device maygenerate a user interface based on the text file. The user interface maydisplay a representation of the optical route. The device may providethe user interface for display and receive a user input via the userinterface. The device may change the representation of the optical routedisplayed by the user interface based on the user input and the networkinformation included in the text file.

According to some possible implementations, a computer-readable mediummay store instructions. The instructions, when executed by one or moreprocessors, may cause one or more processors to receive a text fileincluding network information for an optical network. The networkinformation may include information for an optical route in the opticalnetwork. The instructions may cause the one or more processors togenerate a user interface based on the text file. The user interface maydisplay multiple representations of the optical route. The instructionsmay cause the one or more processors to provide the user interface fordisplay and receive a user input via the user interface. Theinstructions may cause the one or more processors to change between themultiple representations of the optical route displayed by the userinterface based on the user input and the network information includedin the text file.

According to some possible implementations, a method may includereceiving, by a device, a text file including network information for anoptical network. The method may include generating, by the device, auser interface based on the text file. The user interface may include aplurality of view types for viewing different representations of theoptical network. The method may include providing, by the device, theuser interface for display and receiving, by the device, a user inputvia the user interface. The method may include selecting, by the device,a view type included in the plurality of view types based on the userinput. The method may include providing, by the device, a representationof the optical network for display based on the selected view type andthe network information included in the text file, where the differentrepresentations including the representation.

BRIEF DESCRIPTION OF DRAWINGS

FIGS. 1A and 1B are diagrams of an overview of an implementationdescribed herein;

FIG. 2A is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 2B is a diagram of example devices of an optical network that maybe monitored and/or configured according to implementations describedherein;

FIG. 2C is a diagram of example super-channels that may be monitoredand/or configured according to implementations described herein;

FIG. 3 is a diagram of example components of one or more devices and/orsystems of FIG. 2A and/or FIG. 2B;

FIG. 4 is a diagram of example functional components of one or moredevices of FIG. 2A and/or FIG. 2B;

FIG. 5 is a diagram of an example process for receiving and storingoptical network information;

FIG. 6 is a diagram of an example process for providing a user interfacethat displays optical network information;

FIG. 7 is a diagram of an example user interface that displays opticalnetwork information;

FIGS. 8, 9A-9C, 10A, 10B, 11, 12A-12D, 13, 14A-14C, 15-18, 19A-19D, 20A,20B, 21A, 21B, 22A, 22B, 23, 26, 27, 29, and 31-35 are diagrams ofexample elements of a user interface that displays optical networkinformation;

FIGS. 24, 25, 28, 30, 36A, and 36B are diagrams of example datastructures that store information associated with an optical network;

FIG. 37 is a flow chart of an example process for exporting sessioninformation to a text file;

FIG. 38 is a diagram of an example implementation relating to theexample process shown in FIG. 37;

FIG. 39 is a diagram of an example implementation relating to theexample process shown in FIG. 37;

FIG. 40 is a flow chart of an example process for reconstructing a userinterface session based on a text file;

FIG. 41 is a diagram of an example implementation relating to theexample process shown in FIG. 40; and

FIG. 42 is a diagram of an example implementation relating to theexample process shown in FIG. 40.

DETAILED DESCRIPTION

The following detailed description of example embodiments refers to theaccompanying drawings. The same reference numbers in different drawingsmay identify the same or similar elements.

Users of optical networks may want to determine information associatedwith the optical network. Optical network information may be difficultto obtain, aggregate, and display. Implementations described hereinassist a user in obtaining and viewing aggregated optical networkinformation, such as network information associated with networkentities and optical links between the network entities.

Moreover, a user may want to determine information associated with theoptical network, but may not have access to the optical network. Forexample, a user may be tasked with planning a brownfield optical network(e.g., adding to or changing an existing optical network), but theoptical network may be secured and the user may not have permission toaccess the optical network. Accordingly, deployment verification andtroubleshooting for the brownfield optical network is frequentlydifficult due to the limited access to the optical network.Implementations described herein may export session information for auser interface session used to display optical network information, andpermit reconstruction of the user interface session based on the textfile. Thus, a user may obtain and view aggregated optical networkinformation, such as network information associated with networkentities and optical links between the network entities, without havingaccess to the optical network.

As used herein, a “route” and/or an “optical route” may correspond to anoptical path and/or an optical lightpath. For example, an optical routemay specify a path along which light is carried between two or morenetwork entities and/or optical links.

As used herein, an optical link may be an optical fiber, another kind ofphysical connection, and/or a wireless connection used to transmit anoptical channel.

As used herein, an optical channel may be an optical super-channel, asuper-channel group, an optical channel group, a set of spectral slices,an optical control channel (e.g., sometimes referred to herein as anoptical supervisory channel, or an “OSC”), an optical data channel(e.g., sometimes referred to herein as “BAND”), and/or any other opticalsignal transmitted via an optical link, a network entity, and/or anoptical route.

In some implementations, an optical channel may be an opticalsuper-channel. A super-channel may include multiple channels multiplexedtogether using wavelength-division multiplexing in order to increasetransmission capacity. Various quantities of channels may be combinedinto super-channels using various modulation formats to create differentsuper-channel types having different characteristics. Additionally, oralternatively, an optical channel may be a super-channel group. Asuper-channel group may include multiple super-channels multiplexedtogether using wavelength-division multiplexing in order to increasetransmission capacity.

Additionally, or alternatively, an optical channel may be a set ofspectral slices. A spectral slice (a “slice”) may represent a spectrumof a particular size in a frequency band (e.g., 12.5 gigahertz (“GHz”),6.25 GHz, etc.). For example, a 4.8 terahertz (“THz”) frequency band mayinclude 384 spectral slices, where each spectral slice may represent12.5 GHz of the 4.8 THz spectrum. A super-channel may include adifferent quantity of spectral slices depending on the super-channeltype.

FIGS. 1A and 1B are diagrams of an overview 100 of an implementationdescribed herein. As illustrated in FIG. 1A, a user interacting with auser device A may request, from a network administrator device, a userinterface (“UI”) that displays optical network information. The networkadministrator device may request the optical network information fromone or more network entities in an optical network. The networkadministrator device may receive the requested information from thenetwork entities, and may provide the requested UI to user device A. AUI session may be created that allows the optical network information tobe presented in various views based on user input, to permit a user tointeract with the optical network information, and/or to permit the userto perform various functions based on the optical network information.

As illustrated in FIG. 1B, user device A may export session informationfor the UI session to a text file (e.g., a tab separated values (TSV)file). The session information may include all or part of the opticalnetwork information, modified optical network information, and/orinformation generated by user input via the UI during the UI session.The text file may be provided to user device B. User device B may importthe text file and reconstruct the UI session based on the text file.User device B may present the UI for the UI session to a user of userdevice B that allows the optical network information to be presented invarious forms based on user input, allows a user to interact with theoptical network information, and/or allows the user to perform variousfunctions based on the optical network information. In other words, theuser of user device B may be provided with the same UI functionality asthe user of user device A. In this way, user device B may have access tothe same information and functionalities as user device A without havingaccess to the network entities.

FIG. 2A is a diagram of an example environment 200 in which systemsand/or methods described herein may be implemented. Environment 200 mayinclude a network planning system 210 (“NPS 210”), a networkadministrator device 220 (“NA 220”), a user device 230, and an opticalnetwork 240 that includes one or more network entities 250-1 through250-N (N>1) (hereinafter referred to individually as “NE 250” andcollectively as “NEs 250”). Devices of environment 200 may interconnectvia wired connections, wireless connections, or a combination of wiredand wireless connections.

NPS 210 may include one or more devices that gather, process, search,store, and/or provide information in a manner described herein. NPS 210may assist a user in modeling and/or planning an optical network, suchas optical network 240. For example, NPS 210 may assist in modelingand/or planning an optical network configuration, which may includequantities, locations, capacities, parameters, and/or configurations ofNEs 250, characteristics and/or configurations (e.g., capacities) ofoptical links between NEs 250, traffic demands of NEs 250 and/or opticallinks between NEs 250, and/or any other network information associatedwith optical network 240 (e.g., optical device configurations, digitaldevice configurations, etc.). NPS 210 may provide information associatedwith optical network 240 to NA 220 so that a user may view, change,and/or interact with the optical network information.

NA 220 may include one or more devices that gather, process, search,store, and/or provide information in a manner described herein. NA 220may receive the optical network information, and may provide the networkinformation for display on a UI. For example, NA 220 may receive theoptical network information from NPS 210, user device 230, opticalnetwork 240, and/or NEs 250. NA 220 may provide the optical networkinformation to another device, such as user device 230, so that a usermay interact with the optical network information. NA 220 may receiveinformation associated with changes to optical network 240 from anotherdevice (e.g., user device 230). NA 220 may provide informationassociated with the network changes to optical network 240 and/or NEs250 in order to configure optical network 240 based on the informationassociated with network changes. NA 220 may provide informationassociated with network changes to another device, such as user device230, so that a user may interact with the changed network information.

User device 230 may include one or more devices that gather, process,search, store, and/or provide information in a manner described herein.In some implementations, user device 230 may include a computer (e.g., adesktop computer, a laptop computer, a tablet computer, etc.), aradiotelephone, a personal communications system (“PCS”) terminal (e.g.,that may combine a cellular telephone with data processing and datacommunications capabilities), a smart phone, and/or any other type ofcomputation and/or communication device. User device 230 may provideinformation to and/or receive information from other devices, such as NA220. For example, user device 230 may receive network information fromNA 220, and may send information associated with network changes to NA220.

Optical network 240 may include any type of network that uses light as atransmission medium. For example, optical network 240 may include afiber-optic based network, an optical transport network, alight-emitting diode network, a laser diode network, an infrarednetwork, and/or a combination of these or other types of opticalnetworks.

NE 250 may include one or more devices that gather, process, store,and/or provide information in a manner described herein. For example, NE250 may include one or more optical data processing and/or traffictransfer devices, such as an optical node, an optical amplifier (e.g., adoped fiber amplifier, an erbium doped fiber amplifier, a Ramanamplifier, etc.), an optical add-drop multiplexer (“OADM”), areconfigurable optical add-drop multiplexer (“ROADM”), a flexiblyreconfigurable optical add-drop multiplexer module (“FRM”), an opticalsource component (e.g., a laser source), an optical source destination(e.g., a laser sink), an optical multiplexer, an optical demultiplexer,an optical transmitter, an optical receiver, an optical transceiver, aphotonic integrated circuit, an integrated optical circuit, and/or anyother type of device capable of processing and/or transferring opticaltraffic.

In some implementations, NEs 250 may include an OADM and/or a ROADMcapable of being configured to add, drop, multiplex, and demultiplexoptical signals. NE 250 may process and transmit optical signals toother NEs 250 throughout optical network 240 in order to deliver opticaltransmissions.

The number and arrangement of devices and/or networks illustrated inFIG. 2A are provided for explanatory purposes. In practice, there may beadditional devices and/or networks, fewer devices and/or networks,different devices and/or networks, or differently arranged devicesand/or networks than are shown in FIG. 2A. Furthermore, two or more ofthe devices illustrated in FIG. 2A may be implemented within a singledevice, or a single device illustrated in FIG. 2A may be implemented asmultiple, distributed devices. Additionally, or alternatively, one ormore of the devices of environment 200 may perform one or more functionsdescribed as being performed by another one or more of the devices ofenvironment 200.

FIG. 2B is a diagram of example devices of optical network 240 that maybe monitored and/or configured according to implementations describedherein. One or more devices illustrated in FIG. 2B may operate withinoptical network 240, and may correspond to NEs 250. Optical network 240may include one or more optical transmitter devices 260-1 through 260-M(M>1) (hereinafter referred to individually as “Tx device 260” andcollectively as “Tx devices 260”), one or more super-channels 265-1through 265-M (M>1) (hereinafter referred to individually as“super-channel 265” and collectively as “super-channels 265”), amultiplexer (“MUX”) 270, an OADM 275, a demultiplexer (“DEMUX”) 280, andone or more optical receiver devices 285-1 through 285-L (L>1)(hereinafter referred to individually as “Rx device 285” andcollectively as “Rx devices 285”).

Tx device 260 may correspond to NE 250. For example, Tx device 260 mayinclude an optical transmitter and/or an optical transceiver thatgenerates an optical signal. Tx device 260 may include one or morelasers, modulators, digital signal processors, multiplexers, and/or thelike. In some implementations, Tx device 260 may be implemented on oneor more integrated circuits, such as one or more photonic integratedcircuits (PICs), one or more application specific integrated circuits(ASICs), or the like. One or more optical signals may be carried viasuper-channel 265. In some implementations, Tx device 260 may beassociated with one super-channel 265. Additionally, or alternatively,Tx device 260 may be associated with multiple super-channels 265.Additionally, or alternatively, multiple Tx devices 260 may beassociated with one super-channel 265.

MUX 270 may correspond to NE 250. For example, MUX 270 may include anoptical multiplexer that combines multiple input super-channels 265 fortransmission over an output fiber.

OADM 275 may correspond to NE 250. For example, OADM 275 may include aremotely reconfigurable optical add-drop multiplexer. OADM 275 maymultiplex, de-multiplex, add, drop, and/or route multiple super-channels265 into and/or out of a fiber (e.g., a single mode fiber). Asillustrated, OADM 275 may drop super-channel 265-1 from a fiber, and mayallow super-channels 265-2 through 265-M to continue propagating towardRx device 285. Dropped super-channel 265-1 may be provided to a device(not shown) that may demodulate and/or otherwise process super-channel265-1 to output the data stream carried by super-channel 265-1. Asillustrated, super-channel 265-1 may be provisioned for transmissionfrom Tx device 260-1 to OADM 275, where super-channel 265-1 may bedropped.

As further illustrated in FIG. 2B, OADM 275 may add super-channel 265-1′(e.g., 265-1 ^(prime)) to the fiber. Super-channel 265-1′ may includeoptical channels 290 at the same or substantially the same wavelengthsas super-channel 265-1. Super-channel 265-1′ and super-channels 265-2through 265-M may propagate to DEMUX 280.

DEMUX 280 may correspond to NE 250. For example, DEMUX 280 may includean optical de-multiplexer that separates multiple super-channels 265carried over an input fiber. For example, DEMUX 280 may separatesuper-channels 265-1′ and super-channels 265-2 through 265-M, and mayprovide each super-channel 265 to a corresponding Rx device 285.

Rx device 285 may correspond to NE 250. For example, Rx device 285 mayinclude an optical receiver and/or an optical transceiver that receivesan optical signal. Rx device 285 may include one or more lasers,modulators, digital signal processors, multiplexers, and/or the like. Insome implementations, Rx device 285 may be implemented on one or moreintegrated circuits, such as one or more PICs, one or more ASICs, or thelike. One or more optical signals may be received at Rx device 285 viasuper-channel 265. Rx device 285 may convert a super-channel 265 intoone or more electrical signals, which may be processed to output theinformation associated with each data stream carried by optical channels290 included in super-channel 265. In some implementations, Rx device285 may be associated with one super-channel 265. Additionally, oralternatively, Rx device 285 may be associated with multiplesuper-channels 265. Additionally, or alternatively, multiple Rx devices285 may be associated with one super-channel 265.

The number and arrangement of devices illustrated in FIG. 2B areprovided for explanatory purposes. In practice, there may be additionaldevices, fewer devices, different devices, or differently arrangeddevices than are shown in FIG. 2B. Furthermore, two or more of thedevices illustrated in FIG. 2B may be implemented within a singledevice, or a single device illustrated in FIG. 2B may be implemented asmultiple, distributed devices. Additionally, one or more of the devicesillustrated in FIG. 2B may perform one or more functions described asbeing performed by another one or more of the devices illustrated inFIG. 2B. Devices illustrated in FIG. 2B may interconnect via wiredand/or wireless connections.

FIG. 2C is a diagram of example super-channels 265 that may be monitoredand/or configured according to implementations described herein. Asuper-channel, as used herein, may refer to multiple optical channelsthat are simultaneously transported over the same optical waveguide(e.g., a single mode optical fiber). Each optical channel included in asuper-channel may be associated with a particular optical wavelength (orset of optical wavelengths). The multiple optical channels may becombined to create a super-channel using wavelength divisionmultiplexing. For example, the multiple optical channels may be combinedusing dense wavelength division multiplexing, in whichchannel-to-channel spacing may be less than 1 nanometer. In someimplementations, each optical channel may be modulated to carry anoptical signal.

An example frequency and/or wavelength spectrum associated withsuper-channels 265 is illustrated in FIG. 2C. In some implementations,the frequency and/or wavelength spectrum may be associated with aparticular optical spectrum (e.g., C Band, C+Band, CDC Band, etc.). Asillustrated, super-channel 265-1 may include multiple optical channels290, each of which corresponds to a wavelength λ (e.g., λ₁, λ₂, throughλ₁₀) within a first wavelength band. Similarly, super-channel 265-M mayinclude multiple optical channels 290, each of which corresponds to awavelength λ (e.g., λ_(Y-X) through λ_(Y)) within a second wavelengthband. The quantity of illustrated optical channels 290 per super-channel265 is provided for explanatory purposes. In practice, super-channel 265may include any quantity of optical channels 290.

Optical channel 290 may be associated with a particular frequency and/orwavelength of light. In some implementations, optical channel 290 may beassociated with a frequency and/or wavelength at which the intensity oflight carried by optical channel 290 is strongest (e.g., a peakintensity, illustrated by the peaks on each optical channel 290). Insome implementations, optical channel 290 may be associated with a setof frequencies and/or a set of wavelengths centered at a centralfrequency and/or wavelength. The intensity of light at the frequenciesand/or wavelengths around the central frequency and/or wavelength may beweaker than the intensity of light at the central frequency and/orwavelength, as illustrated.

In some implementations, the spacing between adjacent wavelengths (e.g.,λ₁ and λ₂) may be equal to or substantially equal to a bandwidth (or bitrate) associated with a data stream carried by optical channel 290. Forexample, assume each optical channel 290 included in super-channel 265-1(e.g., λ₁ through λ₁₀) is associated with a 50 Gigabit per second(“Gbps”) data stream. In this example, super-channel 265-1 may have acollective data rate of 500 Gbps (e.g., 50 Gbps×10). In someimplementations, the collective data rate of super-channel 265 may begreater than or equal to 100 Gbps. Additionally, or alternatively, thespacing between adjacent wavelengths may be non-uniform, and may varywithin a particular super-channel band (e.g., super-channel 265-1). Insome implementations, optical channels 290 included in super-channel 265may be non-adjacent (e.g., may be associated with non-adjacentwavelengths in an optical spectrum).

Each super-channel 265 may be provisioned in optical network 240 as oneoptical channel and/or as an individual optical channel. Provisioning ofan optical channel may include designating a route and/or path for theoptical channel through optical network 240. For example, an opticalchannel may be provisioned to be transmitted via a set of NEs 250. Insome implementations, NEs 250 may be configured as a ring. Additionally,or alternatively, NEs 250 may be configured in a point-to-pointconfiguration. Provisioning may be referred to as “allocating” and/or“allocation” herein. Even though each super-channel 265 is a compositeof multiple optical channels 290, the optical channels 290 included insuper-channel 265 may be routed together through optical network 240.Additionally, or alternatively, super-channel 265 may be managed and/orcontrolled in optical network 240 as though super-channel 265 includedone optical channel and/or one optical channel at one wavelength.

FIG. 3 is a diagram of example components of a device 300. Device 300may correspond to NPS 210, NA 220, user device 230, and/or NE 250. Insome implementations, NPS 210, NA 220, user device 230, and/or NE 250may include one or more devices 300 and/or one or more components ofdevice 300. As shown in FIG. 3, device 300 may include a bus 310, aprocessor 320, a memory 330, a storage component 340, an input component350, an output component 360, and a communication interface 370.

Bus 310 may include a component that permits communication among thecomponents of device 300. Processor 320 may include a processor (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), etc.), a microprocessor, and/or anyprocessing component (e.g., a field-programmable gate array (FPGA), anapplication-specific integrated circuit (ASIC), etc.) that interpretsand/or executes instructions. Memory 330 may include a random accessmemory (RAM), a read only memory (ROM), and/or another type of dynamicor static storage device (e.g., a flash memory, a magnetic memory, anoptical memory, etc.) that stores information and/or instructions foruse by processor 320.

Storage component 340 may store information and/or software related tothe operation and use of device 300. For example, storage component 340may include a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, a solid state disk, etc.), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of computer-readable medium, along with acorresponding drive.

Input component 350 may include a component that permits device 300 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, amicrophone, etc.). Additionally, or alternatively, input component 350may include a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, an actuator,etc.). Output component 360 may include a component that provides outputinformation from device 300 (e.g., a display, a speaker, one or morelight-emitting diodes (LEDs), etc.).

Communication interface 370 may include a transceiver-like component(e.g., a transceiver, a separate receiver and transmitter, etc.) thatenables device 300 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. Communication interface 370 may permit device 300to receive information from another device and/or provide information toanother device. For example, communication interface 370 may include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a Wi-Fi interface, a cellular network interface, orthe like.

Device 300 may perform one or more processes described herein. Device300 may perform these processes in response to processor 320 executingsoftware instructions stored by a computer-readable medium, such asmemory 330 and/or storage component 340. A computer-readable medium isdefined herein as a non-transitory memory device. A memory deviceincludes memory space within a single physical storage device or memoryspace spread across multiple physical storage devices.

Software instructions may be read into memory 330 and/or storagecomponent 340 from another computer-readable medium or from anotherdevice via communication interface 370. When executed, softwareinstructions stored in memory 330 and/or storage component 340 may causeprocessor 320 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry may be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 3 are provided asan example. In practice, device 300 may include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 3. Additionally, or alternatively, aset of components (e.g., one or more components) of device 300 mayperform one or more functions described as being performed by anotherset of components of device 300.

FIG. 4 is a diagram of example functional elements of a device 400 thatmay correspond to NA 220 and/or user device 230. As illustrated, device400 may include a network information manager 410, a UI manager 420, anda network configurer 430. Each of functional components 410-430 may beimplemented using one or more components of device 300. NA 220 and/oruser device 230 may individually include all of the functionalcomponents illustrated in FIG. 4, or the functional componentsillustrated in FIG. 4 may be distributed singularly or duplicatively inany manner between the devices illustrated in FIG. 2A. In someimplementations, NA 220 and/or user device 230 may include otherfunctional components (not shown) that aid in managing optical networkinformation and/or providing optical network information for display.

Network information manager 410 (“NIM 410”) may perform operationsassociated with managing network information. In some implementations,NIM 410 may receive network information from NPS 210 and/or NEs 250.

Network information received from NPS 210 may include quantities,locations, capacities, parameters, and/or configurations of NEs 250;characteristics and/or configurations (e.g., capacities) of opticallinks between NEs 250; traffic demands of NEs 250 and/or optical linksbetween NEs 250, and/or any other network information associated withoptical network 240 (e.g., optical device configurations, digital deviceconfigurations, etc.). In some implementations, a user may model and/orplan optical network 240 using NPS 210. NIM 410 may receive the networkinformation modeled and/or planned using NPS 210, thus providing initialnetwork information to NIM 410.

The initial network information provided to NIM 410 may be supplementedwith network information received from NEs 250. For example, NEs 250 mayprovide real-time network deployment information to update the initialnetwork information provided by NPS 210. For example, NIM 410 mayreceive network information from NEs 250 that identifies newly-deployedNEs 250 and/or new optical links between NEs 250. Additionally, oralternatively, NIM 410 may receive other network information from NEs250, such as operational information associated with NEs 250 and/oroptical links (e.g., optical link allocation information).

NIM 410 may transmit the network information received from NPS 210and/or NEs 250 to UI manager 420 to provide a UI that displays networkinformation (e.g., on NA 220 and/or user device 230).

UI manager 420 may perform operations associated with managing a UI thatdisplays network information. UI manager 420 may receive networkinformation from NIM 410, and may provide the network information fordisplay on a device, such as NA 220 and/or user device 230. UI manager420 may receive a user request for information (e.g., via the UI), andmay provide the requested information for display on the UI.Additionally, or alternatively, UI manager 420 may receive informationassociated with changes to a network configuration from a userinteracting with a UI (e.g., via NA 220 and/or user device 230). UImanager 420 may provide the information associated with the networkconfiguration changes to network configurer 430 so that optical network240 and/or NEs 250 may be configured in accordance with the changes.

Network configurer 430 may perform operations associated withconfiguring an optical network and/or a network entity associated withan optical network. For example, network configurer 430 may aid inconfiguring optical network 240 and/or NEs 250. Network configurer 430may receive information associated with network configuration changesfrom UI manager 420. Network configurer 430 may communicate theinformation associated with the changes to NEs 250 (and/or other devicesin optical network 240) so that NEs 250 may adjust their configurationin accordance with the network configuration changes. For example,network configurer 430 may provide instructions to NEs 250 that indicatethat NEs 250 are to change a particular parameter. In someimplementations, network configurer 430 may receive informationvalidating a changed configuration from NEs 250, and may provide theconfiguration validation information to UI manager 420 so that thevalidated changes may be displayed on a UI (e.g., on NA 220 and/or userdevice 230).

FIG. 5 is a diagram of an example process 500 for receiving and storingoptical network information. In some implementations, one or moreprocess blocks of FIG. 5 may be performed by one or more components ofNA 220 and/or user device 230.

Process 500 may include receiving optical network information (block510). For example, NIM 410 may receive the optical network informationfrom NPS 210 and/or NEs 250. NIM 410 may request the network informationon a periodic basis (e.g., every second, every minute, every hour, everyday, every week, etc.). Additionally, or alternatively, NIM 410 mayrequest the network information in response to a user request for thenetwork information. Additionally, or alternatively, NPS 210 and/or NEs250 may automatically provide the network configuration information toNIM 410 (e.g., on a periodic basis and/or when a configuration ischanged).

Process 500 may include storing the optical network information (block520). For example, NIM 410 may store the optical network information ina memory associated with NA 220 and/or user device 230. For example, NIM410 may store network information associated with NEs 250 and/or opticallinks between NEs 250, allocation statuses of optical links, alertinformation associated with NEs 250 and/or optical links, etc. NIM 410may associate the stored information with a particular NE 250 and/or aparticular optical route. An optical route may refer to a series of NEs250 that connect a source NE 250 to a destination NE 250 for aparticular optical transmission.

Although FIG. 5 shows example blocks of process 500, in someimplementations, process 500 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 5. Additionally, or alternatively, two or more of theblocks of process 500 may be performed in parallel.

FIG. 6 is a diagram of an example process 600 for providing a userinterface that displays optical network information. In someimplementations, one or more process blocks of FIG. 6 may be performedby one or more components of NA 220 and/or user device 230.

Process 600 may include receiving a request for a UI that displaysoptical network information (block 610). In some implementations, UImanager 420 may receive a request from a user (e.g., interacting with aUI on NA 220 and/or user device 230) for a UI that displays networkinformation associated with a particular optical route. For example, auser may specify an optical route using a UI (e.g., using a button, adrop-down menu or box, a link, a text box, etc.). The user may specify aparticular optical route, NEs 250 associated with an optical route,optical links associated with an optical route, and/or any otherinformation associated with an optical route. In some implementations,UI manager 420 may authenticate the user (e.g., using a user name and/orpassword). Additionally, or alternatively, UI manager 420 may providethe user request to NIM 410.

Process 600 may include determining whether to use stored networkinformation for the request (block 620). In some implementations, NIM410 may determine whether to use stored network information based onwhether the requested information is stored in a memory (e.g., a memoryassociated with NA 220 and/or user device 230). Additionally, oralternatively, NIM 410 may determine whether to use stored networkinformation based on a period of time that has passed since the networkinformation and/or the requested information stored in the memory waslast updated. Additionally, or alternatively, NIM 410 may receive userinput indicating whether to use stored network information or to requestnetwork information from NEs 250.

If NIM 410 determines that stored network information should be used(block 620—YES), process 600 may include providing the stored networkinformation for display on a UI (block 630). In some implementations,NIM 410 may provide the stored network information to UI manager 420 fordisplay on a device (e.g., NA 220 and/or user device 230). Additionally,or alternatively, NIM 410 may provide UI manager 420 with informationthat identifies a date and/or time associated with the stored networkinformation (e.g., when the stored network information was lastupdated).

If NIM 410 determines that stored network information should not be used(block 620—NO), process 600 may include requesting the optical networkinformation from a network entity (block 640). In some implementations,NIM 410 may request user-specified network information from NEs 250associated with a user-specified optical route. NIM 410 may receive therequested network information from NEs 250, and may provide the networkinformation to UI manager 420. In some implementations, NIM 410 mayperiodically request and/or receive network information from NEs 250 andprovide the network information to UI manager 420 for display on a UI.Additionally, or alternatively, NIM 410 may receive network informationfrom NEs 250 when there is a change to the network information so thatthe UI may display real-time network information.

Process 600 may include providing the network information received fromthe network entity for display on a UI (block 650). In someimplementations, NIM 410 may provide the received network information toUI manager 420 for display on a device (e.g., NA 220 and/or user device230). Additionally, or alternatively, NIM 410 may provide a combinationof stored network information and network information received from NEs250 to UI manager 420 for display on a device (e.g., NA 220 and/or userdevice 230). When information and/or a configuration associated with NEs250 changes, the UI may be updated to display real-time informationassociated with NEs 250.

Process 600 may include receiving user-specified changes to the networkinformation (block 660). In some implementations, UI manager 420 and/ornetwork configurer 430 may receive input from a user, via the UI, thatspecifies a change to a parameter associated with an NE 250. Forexample, a user may specify a change to a power parameter, a gainparameter, or any other parameter associated with an NE 250.Additionally, or alternatively, a user may specify whether a parametershould be automatically adjusted on an NE 250 based on a networkcondition.

Process 600 may include providing the user-specified changes to anetwork entity (block 670). In some implementations, network configurer430 may provide information associated with a user-specified parameterto NE 250 so that NE 250 may update its configuration based on theuser-specified parameter. Network configurer 430 may instruct NE 250 toupdate a parameter according to user input.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

FIG. 7 is a diagram of an example user interface 700 (“UI 700”) that maydisplay optical network information. In some implementations, UI 700 maybe displayed by NA 220 and/or user device 230. As illustrated, UI 700may include a user input element 705, a graphical element 710, a tabelement 715, a chart element 720, a tab element 725, a tab element 730,a table element 740, a column element 745, and a cell element 750.Additionally, or alternatively, UI 700 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 7. UI 700 may be updated inreal-time and/or periodically to provide current network configurationinformation.

User input element 705 may provide one or more mechanisms (e.g., adrop-down box, a button, a menu, a link, a text box, a check box, a listbox, a tab, etc.) for a user to provide input. The information displayedon UI 700 may be based on the user input. For example, a user may inputan optical route, a set of NEs 250, and/or a set of optical links (e.g.,between a set of NEs 250). In some implementations, UI 700 may provide amechanism for a user to launch another user interface that may assist auser in selecting an optical route, a set of NEs 250, and/or a set ofoptical links. The user input may be displayed on UI 700. Additionally,or alternatively, information associated with the user inputted opticalroute, set of NEs 250, and/or set of optical links may be displayed onUI 700. In some implementations, UI 700 may provide display options.Information displayed on UI 700 and/or the manner in which informationis displayed on UI 700 may be based on a user-specified display option.

Graphical element 710 may display a representation of an optical route,NEs 250 associated with an optical route, and/or optical linksassociated with an optical route. The representation may includeinformation associated with the optical route, the NEs 250, and/or theoptical links. Graphical element 710 may display the representationbased on user input (e.g., via user input element 705). For example, auser may input an optical route, one or more NEs 250, one or moreoptical links, etc., using user input element 705.

In some implementations, graphical element 710 may display a particularrepresentation based on user input. For example, graphical element 710may display a summary view (discussed herein in connection with FIGS. 8,9A-9C, 10A, and 10B), an optical switching view (discussed herein inconnection with FIGS. 11 and 12A-12D), and/or a field replaceable unit(“FRU”) connectivity view (discussed herein in connection with FIGS. 13.14A-C, 15-18, 19A, 19B, 20A, 20B, 21A, 21B, 22A, and 22B). In someimplementations, a user may select a tab element 715, and graphicalelement 710 may display a particular representation based on the userselection. Additionally, or alternatively, graphical element 710 maydisplay a particular representation based on user input via user inputelement 705.

Chart element 720 may display information associated with an opticalroute, information associated with NEs 250, and/or informationassociated with optical links. Chart element 720 may display theinformation based on user input (e.g., via user input element 705, aselection of an item in graphical element 710, etc.).

In some implementations, chart element 720 may display a particulartable based on user input. For example, chart element 720 may display apower evolution table (discussed herein in connection with FIGS. 23-26),a band cross-section table, (discussed herein in connection with FIGS.27 and 28), and/or a path connectivity table (discussed herein inconnection with FIGS. 29 and 30). In some implementations, a user mayselect a tab element 725 and/or a tab element 730, and chart element 720may display a particular table based on the user selection. In someimplementations, tab element 730 may display a different set of tabsbased on user selection of tab element 725.

Additionally, or alternatively, chart element 720 may display aparticular graph based on user input. For example, chart element 720 maydisplay an optical link power graph (discussed herein in connection withFIG. 31), a band cross-section graph (discussed herein in connectionwith FIG. 32), an optical transport system power graph (discussed hereinin connection with FIG. 33), and/or a gain/loss graph (discussed hereinin connection with FIG. 34). In some implementations, a user may selecta tab element 725 and/or a tab element 730, and chart element 720 maydisplay a particular graph based on the user selection. In someimplementations, tab element 730 may display different sets of tabsbased on user selection of tab element 725.

Table element 740 may display information associated with an opticalroute, information associated with NEs 250, and/or informationassociated with optical links. Table element 740 may display theinformation based on user input (e.g., via user input element 705, aselection of an item in graphical element 710 and/or chart element 720,etc.). In some implementations, table element 740 may display a channelpower table (discussed herein in connection with FIGS. 35, 36A, and36B).

In some implementations, chart element 720 and/or table element 740 maycontain one or more column elements 745 and/or cell elements 750. Columnelement 745 and/or cell element 750 may provide one or more mechanisms(e.g., a clickable element, a selectable element, a link, etc.) for auser to provide input. The information displayed on UI 700 and/or themanner in which information is displayed on UI 700 may be based on theuser input. For example, a user may input, via column element 745 and/orcell element 750, an optical route, a set of network nodes (e.g., NEs250), a set of optical links between network nodes, etc., which may bedisplayed on UI 700 (e.g., in graphical element 710, chart element 720,and/or table element 740).

In some implementations, a user may change a parameter associated withan NE 250 and/or an optical link by interacting with UI 700. Forexample, UI 700 may provide a mechanism (e.g., a button, a clickableelement, a text box, a link, etc.) for a user to change a parameter. Insome implementations, the mechanism may launch another user interfacethat may assist a user in changing a parameter. Additionally, oralternatively, the mechanism may allow a user to directly edit aparameter via UI 700 (e.g., by changing the value of a cell element).

FIG. 8 is a diagram of an example element 800 of a user interface thatdisplays optical network information. Element 800 may be displayed by UI700. Element 800 may include tab element 715, a summary view element805, node elements 810, optical link elements 815, a view selectionelement 820, a route selection element 825, and an option element 830.Additionally, or alternatively, element 800 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 8.

Summary view element 805 may display a representation of NE 250, acapability associated with NE 250, a parameter associated with NE 250,an optical link associated with NE 250, an optical link parameterassociated with NE 250, and/or any other information associated with NE250. Summary view element 805 may be displayed by graphical element 710.In some implementations, summary view element 805 may be displayed basedon user selection of a tab element 715 corresponding to summary viewelement 805, and/or based on user input via user input element 705(e.g., view selection element 820, route selection element 825, and/oroption element 830).

Node element 810 may display a representation of NE 250, a capabilityassociated with NE 250, and/or a parameter associated with NE 250. Nodeelement 810 may display the representation based on user input. Forexample, a user may input (e.g., via a drop-down box, a button, a menu,a text box, etc.) an optical route, a set of NEs 250, a set of opticallinks, etc. (e.g., via route selection element 825). Node element 810may represent NE 250 associated with the user input by displaying arectangle with identifiers (e.g., symbols, text, images, etc.) thatidentify capabilities and/or attributes associated with NE 250.

Optical link element 815 may display a representation of an optical linkand/or an optical link parameter. Optical link element 815 may displaythe representation based on user input. For example, a user may input(e.g., via a drop-down box, a button, a menu, a text box, etc.) anoptical route, a set of NEs 250, a set of optical links, etc. (e.g., viaroute selection element 825). Optical link element 815 may represent anoptical link associated with the user input by displaying an arrowbetween NEs 250 associated with the optical link.

View selection element 820 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) that allows a user toinput a view type. User input of a view type may cause UI 700 and/orsummary view element 805 to display information based on the user-inputview type. A view type may include a control channel view (e.g., asignaling channel view, an optical supervisory channel (“OSC”) view), adata channel view (e.g., a “BAND” view), an optical link terminationview, and/or any combination of these or other views. Herein, a controlchannel view may be referred to as an OSC view, a data channel view maybe referred to as a BAND view, a combined control channel and datachannel view may be referred to as an OTS view, an optical linktermination view may be referred to as an OL view, and a combined datachannel and optical link termination view may be referred to as aBAND/OL view.

An optical fiber may contain a control channel (OSC) and a data channel(BAND). Parameters associated with a fiber as a whole (OTS) may bedifferent from parameters associated with a control channel (OSC) and/ora data channel (BAND) carried on the fiber.

Route selection element 825 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) that allows a user toinput an optical route. A user may input an optical route using anoptical route identifier, a set of NEs 250 that identify an opticalroute, a set of optical links that identify an optical route, an opticalfiber that identifies an optical route, and/or any other informationthat identifies an optical route. UI 700 and/or summary view element 805may display a representation of the identified optical route based onthe user input. For example, node element 810 may display a set of NEs250 associated with the identified optical route, and/or optical linkelement 815 may display a set of optical links associated with theidentified optical route.

As an example, in FIG. 8, a user has selected (via route element 825) anoptical route between node 1 and node 8 (which also include nodes 2-7).As illustrated, summary view element 805 may display a representation ofthe selected optical route. For example, node element 810 may display arepresentation of nodes 1 through 8 (e.g., NE-1 through NE-8) based onthe user selection, as illustrated. Additionally, or alternatively, nodeelement 810 may display information associated with nodes 1 through 8.In some implementations, optical link element 815 may display arepresentation of optical links between one or more nodes that connectnode 1 to node 8 (e.g., arrows between nodes NE-1 and NE-2, arrowsbetween nodes NE-2 and NE-3, etc.), as illustrated. Additionally, oralternatively, optical link element 815 may display informationassociated with optical links between one or more nodes that connectnode 1 to node 8.

Option element 830 may provide a mechanism (e.g., a button, a check box,a drop-down box, a menu, etc.) that allows a user to input displayoptions. In some implementations, option element 830 may include amechanism that permits a user to indicate a desire to show and/or hideparticular display elements. For example, option element 830 may includea mechanism to show and/or hide node element 810, optical link element815, and/or particular information displayed by node element 810 and/oroptical link element 815 (e.g., one or more NEs 250, one or more opticallinks, and/or particular types of information associated with one ormore NEs 250, one or more NE components, and/or one or more opticallinks). Option element 830 may include a mechanism to show and/or hideparticular NEs 250 and/or optical links based on a parameter associatedwith the NEs 250 and/or the optical links (e.g., an add/drop location ofan optical route, an alert associated with an NE 250, etc.)

In some implementations, option element 830 may include a mechanism(e.g., a check box, a button, etc.) that receives user input to displayan optical route in reverse order. For example, summary view element 805may display nodes 1 through 8 in ascending order (NE-1, NE-2, NE-3,etc.) from left to right, as illustrated. Option element 830 may receiveuser input to reverse the order of the displayed nodes, and may displaynodes 1 through 8 in descending order (NE-8, NE-7, NE-6, etc.) from leftto right.

Additionally, or alternatively, option element 830 may include amechanism (e.g., drop-down box, a check box, a button) that receivesuser input to display optical links in one direction (e.g., from left toright, from right to left) or more than one direction (e.g., both fromleft to right and from right to left). For example, summary view element805 may display arrows representing optical links in two directions(e.g., to the left, to the right) between NEs 250, as illustrated.Option element 830 may receive user input to display the optical linkrepresentation (e.g., the arrows), in only one direction (e.g., only tothe left, or only to the right), or in more than one direction (e.g.,both to the left and to the right).

FIG. 9A is a diagram of an example element 900 of a user interface thatdisplays optical network information. Element 900 may be displayed by UI700 (e.g., by summary view element 805, node element 810, and/or opticallink element 815). Element 900 may include node information elements905-950 (hereinafter referred to collectively as “NIEs,” andindividually as “NIE”). Additionally, or alternatively, element 900 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 9A.

NIE 905 may display information that identifies an NE 250. For example,NIE 905 may display an NE identifier (e.g., NE-1, as illustrated). NIE905 may display information that identifies NE 250 based on user input.For example, NIE 905 may display an identifier of NE 250 included in auser-specified optical route.

NIE 910 may display information that identifies a functional capabilityof an NE 250. For example, NIE 910 may display a functional capabilityidentifier (e.g., CDC, C Band, C+ Band, as illustrated). NE 250 may havea functional capability of transmitting and/or receiving optical signalson a particular wavelength/frequency band of an optical spectrum. NE 250may capable of transmitting and/or receiving an optical signal on acolorless band (“C” or “C Band”), an extended colorless band (“C+” or“C+Band”), a colorless, directionless, and contentionless band (“CDC” or“CDC Band”), and/or any other band on an optical spectrum.

NIEs 915-925 may display information that identifies an amplificationcapability of NE 250. An amplification capability may include dopedfiber amplification (“DFA”), erbium doped fiber amplification (“EDFA”),Raman amplification, counter-propagating Raman amplification,co-propagating Raman amplification, and/or any combination of theseamplification capabilities and/or other amplification capabilities.

NIEs 915-925 may use different identifiers (e.g., labels, symbols,colors, text, etc.) to identify different amplification capabilities.For example, NIE 915 may represent EDFA using a triangle. NIEs 920 and925 may represent Raman amplification using an arrow. NIE 920 mayrepresent co-propagating Raman amplification using an arrow that pointsin the same direction as a triangle that represents EDFA and/or an arrowthat points in the same direction as an arrow representing a signaltransmission (e.g., the signal transmission arrow connecting NE-2 toNE-3). NIE 925 may represent counter-propagating Raman amplificationusing an arrow that points in the opposite direction as a triangle thatrepresents EDFA, and/or an arrow that points in the opposite directionas an arrow representing a signal transmission (e.g., the signaltransmission arrow connecting NE-3 to NE-2). In some implementations,NIEs 915-925 may display multiple identifiers to represent multipleand/or hybrid amplification capabilities. For example, NIE 920 mayrepresent a hybrid EDFA and co-propagating Raman amplificationcapability, and NIE 925 may represent a hybrid EDFA andcounter-propagating Raman amplification capability.

NIEs 915-925 may display information that identifies an amplificationdirection capability associated with NE 250. An amplification directioncapability may include an amplification capability in a direction fromone NE 250 to another NE 250. In some implementations, NIEs 915-925 mayuse different locations (e.g., on-screen positions) to displayinformation that identifies an amplification direction capability. Forexample, NIEs 915-925 may display an identifier on a left side of NE 250to represent transmissions to and/or from another NE 250 represented tothe left of NE 250. Similarly, NIEs 915-925 may display an identifier ona right side of NE 250 to represent transmissions to and/or from anotherNE 250 represented to the right of NE 250.

Additionally, or alternatively, an amplification direction may include areceiving direction and/or a transmitting direction. In someimplementations, NIEs 915-925 may use different identifiers to displayinformation that identifies a receiving and/or transmitting direction.Additionally, or alternatively, NIEs 915-925 may use different locations(e.g., on-screen positions) to display information that identifies areceiving direction and/or a transmitting direction. For example, NIEs915-925 may display triangles and/or arrows pointing in differentdirections to represent a receiving direction and/or a transmittingdirection. NIEs 915-925 are described in more detail herein inconnection with FIG. 9B.

FIG. 9B is a diagram of an example element 900 of a user interface thatdisplays optical network information. Element 900 may be displayed by UI700 (e.g., by summary view element 805, node element 810, and/or opticallink element 815). Element 900 may include NIEs 905-950, discussedherein in connection with FIG. 9A. Additionally, or alternatively,element 900 may include node information elements (“NIE”) 955.Additionally, or alternatively, element 900 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 9B.

As illustrated in FIG. 9B, NIE 905 may display information thatidentifies network entities NE-3, NE-4, and NE-5 (e.g., based on userinput of a route between NE-3 and NE-5). NIE 955 may display informationthat identifies components associated with NE-3, NE-4, and NE-5. NE 250may contain another NE 250 as a component. For example, NE 250 mayinclude an optical amplifier, which may be a doped fiber amplifier(identified in the figures as “IAM”) and/or a Raman amplifier(identified in the figures as “IRM”). NIE 955 may display arepresentation of IAM 1-A-1 on NE-3, IAM 2-A-1 on NE-4, IRM 1-A-1 onNE-4, and IRM 2-A-1 on NE-5, as illustrated.

NIEs 915-925 may display a representation of an amplification directionof a node. For example, NIE 915 a may indicate that IAM 1-A-1 of NE-3has an EDFA amplification capability when transmitting optical signalsto IAM 2-A-1 of NE-4. Similarly, NIE 915 b may indicate that IAM 1-A-1of NE-3 has an EDFA amplification capability when receiving opticalsignals from IAM 2-A-1 of NE-4. NIEs 915 c and 925 a may indicate thatIRM 1-A-1 of NE-4 has both an EDFA amplification capability and acounter-propagating Raman amplification capability when receivingoptical signals from IRM 2-A-1 of NE-5.

Returning to FIG. 9A, NIE 930 may display information that identifies aquantity of directions in which NE 250 is capable of transmitting and/orreceiving optical transmissions. For example, NE 250 may include acomponent that is capable of transmitting and/or receiving opticalsignals in nine directions (e.g., to and/or from nine different ports ofother components). In some implementations, NE 250 may include acomponent that is capable of transmitting and/or receiving opticalsignals in three directions. Additionally, or alternatively, NE 250 maybe capable of transmitting and/or receiving signals in any quantity ofdirections. NIE 930 may display an identifier (e.g., a label, a number,a symbol, etc.) that indicates a quantity of directions that NE 250 iscapable of using for optical transmissions (e.g., 9 directions, asillustrated).

NIE 935 may display information that identifies a capability of NE 250.For example, NIE 935 may display an identifier (e.g., a symbol, a label,an image, text, etc.) that indicates that NE 250 is capable oftransmitting and/or receiving optical signals in multiple directions(e.g., four arrows radiating from a central point, as illustrated). Insome implementations, NIE 935 may not display a symbol if NE 250 doesnot have multi-directional capabilities. For example, NE 250 may be anoptical amplifier capable of receiving a signal from one direction andtransmitting the received signal in one direction.

NIEs 940-950 may display information indicating that an opticaltransmission, associated with a user-specified and/or non-user-specifiedoptical link, is added, dropped, and/or transmitted via NE 250.Additionally, or alternatively, NIEs 940-950 may display informationindicating a transmitting direction and/or a receiving direction for theoptical transmission that is added, dropped, and/or transmitted. NIEs940-950 may display an identifier (e.g., a single-headed arrow, adouble-headed arrow, a line, a symbol, etc.) that indicates that thetransmission is added, dropped, and/or transmitted at NE 250.

For example, NIE 940 may indicate that an optical transmission, receivedfrom a node displayed to the left of NE-1, is dropped at NE-1.Alternatively, NIE 940 may indicate that an optical transmission isadded at NE-1 and transmitted to a node displayed to the left of NE-1.NIE 945 may indicate that an optical transmission, received from a nodedisplayed to the right of NE-1, is dropped at NE-1. Alternatively, NIE945 may indicate that an optical transmission is added at NE-1 andtransmitted to a node displayed to the right of NE-1. NIE 950 mayindicate that an optical transmission is transmitted, via NE-1, betweena node displayed to the left of NE-1 and a node displayed to the rightof NE-1. NIEs 940-950 are described in more detail herein in connectionwith FIG. 9C.

FIG. 9C is a diagram of an example element 900 of a user interface thatdisplays optical network information. Element 900 may be displayed by UI700 (e.g., by summary view element 805 and/or node element 810). Element900 may include NIEs 905-950, discussed herein in connection with FIG.9A. Additionally, or alternatively, element 900 may include NIEs960-990. NIEs 960-990 may correspond to NIEs 940, 945, and/or 950.Additionally, or alternatively, element 900 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 9C.

NIE 960 may indicate that a transmission, carried on a user-specifiedoptical link and received from a node displayed to the right of NE-1, isdropped at NE-1 (e.g., by displaying a double-headed arrow with one headpointing right and the other head pointing down). Alternatively, NIE 960may indicate that a transmission, carried on a user-specified opticallink, is added at NE-1 and transmitted to a node displayed to the rightof NE-1 (e.g., by displaying a double-headed arrow with one headpointing down and the other head pointing right). NIE 960 may alsoindicate that there are no non-user-specified optical links carrying atransmission, via NE-1, between a node displayed to the left of NE-1 anda node displayed to the right of NE-1.

NIE 965 may indicate that a transmission, carried on a user-specifiedoptical link and received from a node displayed to the right of NE-2, isdropped at NE-2 (e.g., by displaying a double-headed arrow with one headpointing right and the other head pointing down). Alternatively, NIE 965may indicate that a transmission, carried on a user-specified opticallink, is added at NE-2 and transmitted to a node displayed to the rightof NE-2 (e.g., by displaying a double-headed arrow with one headpointing down and the other head pointing right). NIE 965 may alsoindicate that there is a non-user-specified optical link carrying atransmission, via NE-2, between a node displayed to the left of NE-2 anda node displayed to the right of NE-2 (e.g., by displaying adouble-headed arrow with one head pointing left and the other headpointing right).

NIE 970 may indicate that a transmission, carried on a user-specifiedoptical link and received from a node displayed to the left of NE-3, isdropped at NE-3 (e.g., by displaying a double-headed arrow with one headpointing left and the other head pointing down). Alternatively, NIE 970may indicate that a transmission, carried on a user-specified opticallink, is added at NE-3 and transmitted to a node displayed to the leftof NE-3 (e.g., by displaying a double-headed arrow with one headpointing down and the other head pointing left). NIE 970 may alsoindicate that there are no non-user-specified optical links carrying atransmission, via NE-3, between a node displayed to the left of NE-3 anda node displayed to the right of NE-3.

NIE 975 may indicate that a transmission, carried on a user-specifiedoptical link and received from a node displayed to the left of NE-4, isdropped at NE-4 (e.g., by displaying a double-headed arrow with one headpointing left and the other head pointing down). Alternatively, NIE 975may indicate that a transmission, carried on a user-specified opticallink, is added at NE-4 and transmitted to a node displayed to the leftof NE-4 (e.g., by displaying a double-headed arrow with one headpointing down and the other head pointing left). NIE 975 may alsoindicate that there is a non-user-specified optical link carrying atransmission, via NE-4, between a node displayed to the left of NE-4 anda node displayed to the right of NE-4 (e.g., by displaying adouble-headed arrow with one head pointing left and the other headpointing right).

NIE 980 may indicate that a user-specified optical link and/or anon-user-specified optical link is carrying a transmission, via NE-5,between a node displayed to the left of NE-5 and a node displayed to theright of NE-5 (e.g., by displaying a double-headed arrow with one headpointing left and the other head pointing right).

NIE 985 may indicate that that a user-specified optical link is carryinga transmission, via NE-6, between a node displayed to the left of NE-6and a node displayed to the right of NE-6 (e.g., by displaying adouble-headed arrow with one head pointing left and the other headpointing right). NIE 985 may also indicate that a transmission, carriedon a non-user-specified optical link and transmitted to or received froma node displayed to the left of NE-6, is added or dropped at NE-6 (e.g.,by displaying a double-headed arrow with one head pointing left and theother head pointing down). NIE 985 may also indicate that atransmission, carried on a non-user-specified optical link andtransmitted to or received from a node displayed to the right of NE-6,is added or dropped at NE-6 (e.g., by displaying a double-headed arrowwith one head pointing right and the other head pointing down).

NIE 990 may indicate that NE 250 is only capable of performingamplification (e.g., by not displaying any double-headed arrows). Forexample, NE-7 may not be capable of adding and/or dropping an opticaltransmission and/or may not be capable of transmitting an opticaltransmission in multiple directions.

FIG. 10A is a diagram of an example element 1000 of a user interfacethat displays optical network information. Element 1000 may be displayedby UI 700 (e.g., by summary view element 805, node element 810, and/oroptical link element 815). Element 1000 may include link informationelements 1005-1030 (hereinafter referred to collectively as “LIEs,” andindividually as “LIE”). Additionally, or alternatively, element 1000 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 10A.

Element 1000 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). In some implementations, when a user inputs a data channel view(e.g., BAND), element 1000 may display a representation and/or aparameter (e.g., a power parameter, a span loss parameter, a gainparameter, etc.) associated with a data channel of a fiber.Additionally, or alternatively, when a user inputs a control channelview (e.g., OSC), element 1000 may display a representation and/or aparameter (e.g., a power parameter, a span loss parameter, an addressparameter, etc.) associated with the control channel. For example, FIG.10A may represent elements that are displayed when a user has input adata channel view (e.g., BAND), a combined control channel and datachannel view (e.g., OTS), and/or a combined data channel and opticallink termination view (e.g., BAND/OL).

LIE 1005 may display information that identifies an amount of opticalpower transmitted (“OPT”) from one NE 250 to another NE 250 via anoptical link. In a data channel view, OPT may represent OPT associatedwith a data channel. In a control channel view, OPT may represent OPTassociated with a control channel. In a combined control channel anddata channel view, OPT may represent OPT associated with a combinedchannel (e.g., at a fiber level). OPT may be displayed in any unit ofpower, such as decibels per watt (“dBW”), decibels per milliwatt(“dBm”), etc.

LIE 1010 may display information that identifies an amount of opticalpower received (“OPR”) from NE 250 to another NE 250 via an opticallink. In a data channel view, OPR may represent OPR associated with adata channel. In a control channel view, OPR may represent OPRassociated with a control channel. In a combined control channel anddata channel view, OPR may represent OPR associated with a combinedchannel (e.g., at a fiber level). OPR may be displayed in any unit ofpower, such as dBw, dBm, etc.

LIE 1015 may display information that identifies a fiber type associatedwith an optical link. A fiber type may include a single-mode opticalfiber (“SMF”), a multi-mode optical fiber (“MMF”), a graded-indexoptical fiber (“GIF”), or any other type of optical fiber. LIE 1015 mayuse different identifiers (e.g., labels, symbols, colors, text, etc.) toidentify different fiber types.

LIE 1020 may display information that identifies a span loss parameterof an optical link. A span loss parameter may identify an amount ofpower lost by an optical signal on an optical link between two NEs 250.A span loss parameter may include a span loss (“SL”), an expected spanloss (“ESL”), a net span loss (“NSL”), and/or any other type of spanloss parameter. A span loss parameters may be displayed in any unit ofpower, such as dBw, dBm, etc.

UI 700 may display different span loss parameters based on a type ofamplification capability associated with NE 250. For example, UI 700 maydisplay SL and/or ESL when EDFA is used to amplify the optical signal atNE 250. SL may identify the actual amount of power lost by an opticalsignal on an optical link between two NEs 250 (e.g., OPT of a signal atNE-3 may equal 7, and the SL of the signal may be 2, so that OPR of thesignal at NE-4 is equal to 5). ESL may identify the amount of powerexpected to be lost by an optical signal on an optical link between twoNEs 250 (e.g., based on historical data, a fiber type, a transmissiondistance, an amplification type, etc.).

UI 700 may display SL, ESL, and/or NSL when Raman amplification (e.g.,co-propagating and/or counter-propagating) is used to amplify theoptical signal at NE 250. NSL may identify the amount of power thatwould have been lost between two NEs 250 if Raman amplification had notoccurred.

LIE 1025 may display information that identifies a gain parameterassociated with an optical link and/or an NE 250. A gain parameter mayidentify an amount of power gained by an optical signal due toamplification by NE 250. A gain parameter may include a current gain(“CG”), a target gain (“TG”), a Raman gain (“RG”), and/or any other typeof gain parameter. A gain parameter may be displayed in any unit ofpower, such as dBw, dBm, etc.

UI 700 may display different gain parameters based on a type ofamplification capability associated with NE 250. For example, UI 700 maydisplay CG and/or TG when EDFA is used to amplify the optical signal atNE 250. CG may identify an actual amount of power gained by an opticalsignal due to EDFA amplification at NE 250 (e.g., NE-4 may receive asignal with OPR of 5, may amplify the signal with a CG of 2, and maytransmit the signal with an OPT of 7). TG may identify a target amountof power gain that NE 250 should apply to a signal using EDFA and/orRaman amplification (e.g., based on an amount of power necessary toreach another NE 250, such as an adjacent NE 250 and/or a destination NE250).

UI 700 may display CG, TG, and/or RG when Raman amplification (e.g.,co-propagating and/or counter-propagating) is used to amplify theoptical signal at NE 250. RG may identify an actual amount of powergained by an optical signal due to Raman amplification at NE 250. Forexample, a signal transmitted from NE-5 to NE-4 may arrive with an OPRof 5, may be amplified with a Raman gain of 1 and an EDFA gain of 1, fora total CG of 2, and may be transmitted from NE-4 to NE-3 with an OPT of7).

LIE 1030 may display information that identifies an alert (e.g., aproblem, an issue, a warning, a malfunction, a notification, etc.)associated with an optical link between two NEs 250. For example, LIE1030 may indicate that an optical link is unable to transmit a signal(e.g., because a fiber has been cut, damaged, degraded, etc.). LIE 1030may display an identifier (e.g., an image, text, a label, a color, etc.)to identify the problem associated with the optical link. For example,LIE 1030 may display an image of scissors to indicate that an opticallink is unable to transmit a signal between NE-3 and NE-4, asillustrated. In some implementations, LIE 1030 may display differentidentifiers to represent different problems associated with an opticallink.

In some implementations, LIE 1030 may provide a mechanism (e.g., aclickable element, a button, a link, etc.) that allows a user toindicate a desire to view alert information associated with an alert.For example, a user may click on LIE 1030, and UI 700 may displayinformation associated with an alert identified by LIE 1030. Alertinformation may include information that identifies an NE 250 associatedwith an alert, information that identifies an optical link associatedwith an alert, information that describes an alert, information thatdescribes conditions that caused the alert, information that identifiesa date and/or time associated with the alert (e.g., when the conditionsthat caused the alert arose), information that describes a solution toremedy the alert, and/or other information associated with an alert.

FIG. 10B is a diagram of an example element 1000 of a user interfacethat displays optical network information. Element 1000 may be displayedby UI 700 (e.g., by summary view element 805, node element 810, and/oroptical link element 815). Element 1000 may include LIEs 1005-1030,discussed herein in connection with FIG. 10A. Additionally, oralternatively, element 1000 may include LIEs 1035. Additionally, oralternatively, element 1000 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 10B.

Element 1000 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, FIG. 10B may represent elements that are displayedwhen a user has input a control channel view (e.g., OSC).

LIE 1035 may display information that identifies an address parameter ofa control channel (e.g., an optical supervisory channel) associated withNE 250. For example, LIE 1035 may identify an internet protocol (“IP”)address and/or a subnet mask address associated with a control channelon NE 250.

FIG. 11 is a diagram of an example element 1100 of a user interface thatdisplays optical network information. Element 1100 may be displayed byUI 700. Element 1100 may include tab element 715, view selection element820, route selection element 825, option element 830, an opticalswitching view element 1105, a route summary view element 1110, and aroute detail view element 1115. Additionally, or alternatively, element1100 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 11.

Optical switching view element 1105 may display a representation of NEs250, a representation of optical links between NEs 250, and/orinformation associated with the represented NEs 250 and/or therepresented optical links. Optical switching view element 1105 may bedisplayed by graphical element 710. In some implementations, opticalswitching view element 1105 may be displayed based on user selection ofa tab element 715 corresponding to optical switching view element 1105,and/or based on user input via user input element 705 (e.g., viewselection element 820, route selection element 825, and/or optionelement 830).

View element 1110 and/or 1115 may display a representation of NEs 250, arepresentation of optical links between NEs 250, and/or informationassociated with the represented NEs 250 and/or the represented opticallinks. In some implementations, view element 1110 and/or 1115 maycorrespond to summary view element 805, and may display node element810, optical link element 815, NIEs 905-990, and/or LIEs 1005-1030. Viewelement 1110 and/or 1115 may display information associated withelements 810, 815, 905-990, and 1005-1030 based on user input (e.g., viauser input element 705). Additionally, or alternatively, view element1110 and/or 1115 may display NEs 250 and/or optical links associatedwith a user-specified route and/or associated with particular criteria(e.g., NEs 250 where an optical transmission is added, dropped, and/ortransmitted, NEs 250 associated with a problem, etc.).

View selection element 820 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) for a user to input aview type. User input of a view type may cause UI 700 and/or opticalswitching view element 1105 to display information based on the viewtype. In some implementations, view selection element 820 may bedisabled when UI 700 is displaying optical switching view element 1105.

Route selection element 825 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) that allows a user toinput an optical route to be displayed by view element 1110 and/or 1115.The user may input an optical route identifier, a set of NEs 250 thatidentify an optical route, a set of optical links that identify anoptical route, and/or any other information that identifies an opticalroute. In some implementations, view element 1110 and/or 1115 maydisplay the identified optical route based on the user input.Additionally, or alternatively, view element 1110 and/or 1115 maydisplay a subset of NEs 250 and/or optical links associated with theidentified optical route based on particular criteria (e.g., auser-specified criteria).

For example, in FIG. 11, a user has selected (via route element 825) anoptical route between node 1 and node 8. View element 1110 and/or 1115may display a representation of the selected optical route.Additionally, or alternatively, view element 1110 and/or 1115 maydisplay particular NEs 250 and/or optical links in the selected opticalroute based on particular criteria (e.g., NEs 250 where an opticaltransmission is added, dropped, and/or transmitted, NEs 250 that areexperiencing a problem, error, or issue, etc.). For example, viewelement 1110 and/or 1115 may display a representation of nodes 1, 4, 7,and 8 (e.g., NE-1, NE-4, NE-7, and NE-8) based on nodes 1, 4, 7, and 8being in the selected optical route and/or meeting a particularcriteria, as illustrated. Additionally, or alternatively, view element1110 and/or 1115 may display information associated with displayed NEs250 and/or displayed optical links.

Option element 830 may provide a mechanism (e.g., a button, a check box,a drop-down box, a menu, etc.) that allows a user to input displayoptions, as discussed herein in connection with FIG. 8.

FIG. 12A is a diagram of an example element 1200 of a user interfacethat displays optical network information. Element 1200 may be displayedby UI 700 (e.g., by optical switching view element 1105). Element 1200may include route summary view element 1110 and route detail viewelement 1115, as discussed herein in connection with FIG. 11.Additionally, or alternatively, element 1200 may include a node displayelement 1205, a component display element 1210, an optical link displayelement 1215, a connection point display element 1220, an add/dropdisplay element 1225, a route direction element 1230, a local routeelement 1235, a source/destination element 1240, and an alert element1245. Additionally, or alternatively, element 1200 may include fewerelements, additional elements, different elements, or differentlyarranged elements than those illustrated in FIG. 12A.

Node display element 1205 may provide information associated withnetwork nodes (e.g., NEs 250). For example, node display element 1205may display a representation of nodes associated with a particularoptical route (e.g., a user-specified route connecting multiple NEs250), an identification of the displayed nodes (e.g., NE-1, NE-4, NE-7,and NE-8, as illustrated), and/or other information associated withnodes. Node display element 1205 may display a particular node inoptical network 240 based on user input of a node, user input of anoptical route associated with a node, and/or user input of otherinformation associated with a node (e.g., via user input element 705).Node display element 1205 may display a summary representation of a nodein route summary view element 1110, and may display a detailedrepresentation of a node in route detail view element 1115, asillustrated. In some implementations, a node may be displayed in routedetail view element 1115 relative to a node displayed in route summaryview element 1110 (e.g., NE-1 in route detail view element 1115 may bedisplayed directly below NE-1 in route summary view element 1110, asillustrated).

Component display element 1210 may provide information associated withcomponents of a displayed node (e.g., NE 250). A node may include one ormore components (e.g., NEs 250). For example, NE-1 may represent an IAMand a ROADM that includes multiple FRMs. In some implementations,component display element 1210 may display a representation of acomponent, an identification of a component (e.g., IAM “1-A-1” and FRM“2-A-2-L1” on NE-1, as illustrated), and/or other information associatedwith a component.

In some implementations, component display element 1210 may include acomponent label that displays information that identifies a powerparameter associated with a component. A power parameter may include anOPR at a component, an OPT at a component, and/or a power adjustmentmade to an optical transmission at a component, (e.g., a power offset,an increase or decrease of power, etc.). For example, a component labelmay indicate that a component is associated with an OPT of −7 and an OPRof −6, and a power offset (“PO”) of −1, as illustrated (e.g., at FRM2-A-2-L1 on NE-1). Additionally, or alternatively, a component label maydisplay other parameters associated with a component (e.g., a gainparameter, an address parameter, etc.).

Optical link display element (“OLDE”) 1215 may provide a representationof one or more optical links that may transmit a signal betweendisplayed nodes. In some implementations, OLDE 1215 may display one ormore optical links that are assigned and/or being used to carry signalsbetween the displayed nodes.

OLDE 1215 may display an optical link in a particular manner dependingon characteristics of the optical link, such as a quantity of spectralslices associated with the optical link (e.g., 20 slices, 32 slices,etc.), a relative position of the associated spectral slices within anoptical spectrum (e.g., slices 1-20 may occupy a different wavelengthand/or position than slices 21-54), an optical link type associated withthe optical link (e.g., a bandwidth and/or modulation format associatedwith an optical link), an allocation status associated with the opticallink (e.g., assigned, used, blocked, and/or available), an alert statusassociated with the optical link (e.g., in service, out of service,misconfigured, not optically viable, and/or other alerts), and/or otherinformation associated with a displayed optical link.

OLDE 1215 may display an optical link in a particular and/or relativeposition (e.g., a position on a display) to convey informationassociated with the optical link. For example, OLDE 1215 may display anoptical link in a particular position based on the spectral slicesassociated with the optical link. In some implementations, optical linksmay be displayed in an order or a sequence, with the first optical linkincluding spectral slices at the beginning of an optical spectrum (e.g.,slice 1), and the last optical link including spectral slices at the endof the spectrum (e.g., slice 384). OLDE 1215 a illustrates a firstoptical link on top of a stack of optical links because the firstoptical link is associated with spectral slices 1-20.

OLDE 1215 may display an optical link using a particular and/or relativesize to convey information associated with the optical link. Forexample, OLDE 1215 may display an optical link using a size that isproportional to the quantity of spectral slices included in the opticallink. The quantity of spectral slices included in an optical link maydepend on an optical link type (e.g., a super-channel type). Asillustrated, OLDE 1215 a may display a first super-channel of type“QPSK-500,” which includes 20 spectral slices, and OLDE 1215 b maydisplay a second super-channel of type “QPSK-1000,” which includes 32spectral slices. The second super-channel may be displayed in a moreprominent manner (e.g., larger, bolder, in a different color, etc.) thanthe first super-channel, as illustrated, because the secondsuper-channel includes more spectral slices than the firstsuper-channel.

OLDE 1215 may display an optical link using an optical link label toconvey information associated with the optical link. An optical linklabel may provide an indication of an optical link identifier (e.g., anumber) associated with an optical link, an optical link type associatedwith an optical link, a capacity of an optical link, an allocationstatus associated with an optical link, an alert status associated withan optical link, and/or other characteristics associated with an opticallink. For example, OLDE 1215 a may display an optical link label thatprovides an indication of an optical link identifier associated with theoptical link (e.g., “1”), a bandwidth associated with the optical link(e.g., “500” Gbps), a modulation format associated with the optical link(e.g., “QPSK”), and an optical link type associated with the opticallink (e.g., “QPSK-500”), as illustrated.

In some implementations, an optical link may be an “open wave,” where auser may input a set of spectral slices to be included in the opticallink. Open wave may allow optical signals to be transmitted over any setof spectral slices. For example, OLDE 1215 c may represent a set of tenspectral slices allocated using open wave, labeled “OW-1/QPSK.”

In some implementations, an optical link label may display informationthat identifies a power parameter associated with an optical link. Apower parameter may include an amount of power transmitted over anoptical link (e.g., an OPT at one end of the optical link and an OPR atanother end of the optical link). OPR and/or OPT may be displayed in onedirection or in both directions. Additionally, or alternatively, a powerparameter may include a PO at a node associated with an optical link(e.g., a transmitting node and/or a receiving node). Additionally, oralternatively, an optical link label may display information thatidentifies other parameters associated with an optical link (e.g., aspan loss parameter, a gain parameter, etc.).

In some implementations, information displayed by an optical link labelmay only be displayed on one optical link representation in a span ofassociated optical links. For example, optical links 6, 7, 8, 9 ss, 10,and 12 between NE-1 and NE-4 may display an optical link modulationformat and an optical link bandwidth. These characteristics may not bedisplayed on the optical link representations between NE-4 and NE-7, andbetween NE-7 and NE-8. In some implementations, information displayed byan optical link label may only be displayed on the first optical link inthe span.

OLDE 1215 may display an optical link using a particular color and/orpattern in order to convey information associated with the optical link.For example, OLDE 1215 may display an optical link using a particularcolor to indicate an allocation status associated with the optical link.For example, OLDE 1215 may display an assigned optical link using afirst color, may display a used optical link using a second color, maydisplay a blocked optical link and/or a set of spectral slices using athird color, and may display an available optical link using a fourthcolor.

An allocation status may include, for example, assigned, used, blocked,and/or available. In some implementations, an assigned status mayindicate that an optical link has been assigned to transmit opticalsignals, but is not currently transmitting optical signals.Additionally, or alternatively, an assigned status may indicate that anoptical link has been assigned to a component (e.g. an FRM) and/or across-connect (e.g., a termination point on an FRM) on one node (e.g.,on NE-4), but has not been assigned to a component and/or across-connect on another node (e.g., on NE-7). OLDE 1215 may displayassigned optical links using a first color.

In some implementations, a used status may indicate that an optical linkis currently transmitting a signal. Additionally, or alternatively, aused status may indicate that an optical link is associated withcomponents (e.g., FRMs) and/or cross-connects (e.g., termination pointson FRMs) on both nodes that the optical link connects (e.g., NE-1 andNE-4). OLDE 1215 may display used optical links using a second color.

In some implementations, a blocked status may indicate that an opticallink and/or a set of spectral slices are unavailable for allocation. Forexample, an optical link may be blocked when there is not enoughcapacity to support allocation of the optical link and/or spectralslices using a particular optical link type. Additionally, oralternatively, a blocked status may indicate that an optical link and/ora set of spectral slices have not been configured for allocation betweennodes. OLDE 1215 may display used optical links using a third color. Insome implementations, OLDE 1215 may not display blocked optical linksand/or spectral slices (e.g., there may be blank space to representblocked optical links and/or spectral slices, as illustrated).

In some implementations, an available status may indicate that anoptical link is available for data transmission (e.g., the optical linkis not assigned, used, or blocked). Additionally, or alternatively, anavailable status may indicate that an optical link is not associatedwith a component or a cross-connect on either node that the optical linkconnects. OLDE 1215 may display available optical links using a fourthcolor.

Connection point display element (“CPDE”) 1220 may provide an indicationof an optical link connection point (e.g., a port) on a component (e.g.,an FRM) associated with a node (e.g., NE 250). CPDE 1220 may provide anindication of an allocation status for a connection point. For example,CPDE 1220 may display a line connecting allocated (e.g., used and/orassigned) connection points to allocated optical links. In someimplementations, the line may be displayed in the same color as thesuper-channel to which it is connected in order to indicate anallocation status of the connection point. Additionally, oralternatively, connection points that have not been allocated may bedisplayed without a line connecting the connection point to an opticallink.

Add/drop display element (“ADDE”) 1225 may provide an indication oftransmissions (e.g., via optical links) that are added or dropped at adisplayed node (e.g., NE 250). In some implementations, ADDE 1225 maydisplay a particular shape (e.g., a square), connected to an opticallink, to indicate an add/drop location of a transmission. Asillustrated, ADDE 1225 may display a square on NE-4 to indicate that thetransmission carried by optical link “1/QPSK-500” between NE-4 and NE-7is added or dropped at NE-4. In some implementations, ADDE 1225 may usea different indicator for an added transmission than for a droppedtransmission.

Route direction element (“RDE”) 1230 may provide an indication of aroute (e.g., an optical link) that has been allocated between adisplayed component (e.g., FRM 2-A-7-L1 on NE-4) and a component that isnot displayed. Additionally, or alternatively, RDE 1230 may indicatethat an optical transmission is being routed between a displayedcomponent and a non-displayed component. For example, UI 700 may displayFRMs 2-A-7-L1 and 2-A-2-L1 on NE-4, as illustrated. There may be otherFRMs on NE-4 that are not displayed by UI 700. RDE 1230 may provide anindication that a route has been allocated between FRM 2-A-7-L1 on NE-4(which is displayed by UI 700) and one of the other FRMs on NE-4 that isnot displayed by UI 700. In some implementations, RDE 1230 may display aparticular shape (e.g., a circle) connected to an optical link toprovide this indication. As illustrated, RDE 1230 may display a circleon NE-4 to indicate that the transmission associated with optical link“2/QPSK-500” between NE-4 and NE-7 is routed between FRM 2-A-7-L1 on NE4and another FRM (one that is not displayed on UI 700) on NE-4 other thanFRM 2-A-2-L1 (which is displayed on UI 700).

Local route element 1235 may provide an indication of a route that hasbeen allocated between displayed components (e.g., FRMs displayed by UI700). Additionally, or alternatively, local route element 1235 mayindicate that an optical transmission is being routed between twodisplayed components. For example, local route element 1235 may displaya line connecting allocated optical links. In some implementations, theline may be displayed in the same color as an optical link to which itis connected in order to indicate an allocation status of the route. Asillustrated, local route element 1235 may display a line on NE-4connecting optical link “10/QPSK-1000” between NE-1 and NE-7. The lineconnects connection points on FRM 2-A-2-L1 and FRM 2-A-7-L1 on NE-4 toindicate that the route is allocated between these FRMs (both of whichare displayed on UI 700).

Source/destination element 1240 may provide a representation of a sourcecomponent and/or a destination component associated with an opticallink. Source/destination element 1240 may display an identifier (e.g., alabel, text, a number, an image, etc.) that identifies a sourcecomponent, a destination component, a port on a source component, and/ora port on a destination component (e.g., port L1 on component 1-A-4,illustrated as “1-A-4-L1”). Source/destination element 1240 may bedisplayed as connected to an add/drop display element 1225, asillustrated.

In some implementations, source/destination element 1240 may include asource/destination component label that displays information thatidentifies a power parameter associated with a source and/or destinationcomponent. A power parameter may include an OPR at a component, an OPTat a component, and/or a PO at a component. For example, asource/destination component label may indicate that a component isassociated with an OPT of −7 and an OPR of −6, as illustrated (e.g., atsource/destination component 1-A-4-L1 on NE-1). Additionally, oralternatively, a source/destination component label may display otherparameters associated with a source and/or destination component (e.g.,a gain parameter, an address parameter, etc.).

Alert element 1245 may provide an indication of an alert (e.g., anerror, a notification, an alarm, a warning, etc.) associated with anoptical link, a component, a connection point (e.g., a port, anadd/drop, a cross-connect, etc.), a node (e.g., NE 250), and/or anyother element of an optical network. For example, an alert may beassociated with a cross-connect problem associated with a node, aservice state associated with an optical link, a configuration problemassociated with an optical link, an optical viability problem associatedwith an optical link and/or route, and/or any other alert that mayconvey information (e.g., an issue, problem, alarm, error, etc.)associated with an optical network.

Alert element 1245 may display an alert in a particular manner based ona severity level associated with the alert. For example, an alert withhigh severity may be displayed in red, an alert with medium severity maybe displayed in orange, and an alert with low severity may be displayedin yellow. Alert element 1245 may display an indication of an alert inroute summary view element 1110 and/or route detail view element 1115.For example, source/destination component 3-A-1-L1 on NE-1 may beassociated with a high severity alert. Alert element 1245 may displaysource/destination component 3-A-1-L1 in red in route detail viewelement 1115, and may display a red outline around NE-1 in route summaryview element 1110.

In some implementations, alert element 1245 may provide a mechanism(e.g., a clickable element, a button, a link, etc.) that allows a userto indicate a desire to view alert information associated with an alert.For example, a user may click on alert element 1245, and UI 700 maydisplay information associated with an alert identified by alert element1245. Alert information may include information that identifies an NE250 associated with an alert, information that identifies an opticallink associated with an alert, information that describes an alert,information that describes conditions that caused the alert, informationthat identifies a date and/or time associated with the alert (e.g., whenthe conditions that caused the alert arose), information that describesa solution to remedy the alert, and/or other information associated withan alert.

FIG. 12B is a diagram of an example element 1200 of a user interfacethat displays optical network information. Element 1200 may be displayedby UI 700 (e.g., by optical switching view element 1105). Element 1200may include route detail view element 1115, as discussed herein inconnection with FIG. 11. Additionally, or alternatively, element 1200may include a component alert element 1250, an optical link alertelement 1255, and a cross-connect alert element 1260. Additionally, oralternatively, element 1200 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 12B.

Component alert element (“CAE”) 1250 may provide an indication of amisconfiguration between a source component on one node and adestination component on another node. A misconfiguration may be adifferent configuration at a source component and a destinationcomponent that prevents and/or degrades an optical transmission betweenthe source component and the destination component. As illustrated, CAE1250 may display an exclamation point (“!”) and/or another notificationon source component 1-A-1-L1 of NE-1 and/or on destination component1-A-1-L1 of NE-8 to indicate a configuration mismatch between thesecomponents.

Optical link alert element (“OLAE”) 1255 may provide an indication of analert (e.g., a problem, an issue, a warning, a notification, etc.)associated with an optical link. For example, OLAE 1255 may provide anindication of a service state of an optical link. A service state mayinclude in-service or out-of-service. As illustrated, OLAE 1255 maydisplay an exclamation point (“!”) and/or another notification onoptical link “13/QPSK-500” between NE-1 and NE-4 to indicate thatoptical link 13 is out of service between NE-1 and NE-4.

Additionally, or alternatively, OLAE 1255 may provide an indication of aconfiguration problem associated with an optical link. A configurationproblem may indicate that a modulation format configured on a connectionpoint (e.g., a cross-connect) of one node associated with an opticallink does not match a modulation format configured on a connection pointof another node associated with the optical link. As illustrated, OLAE1255 may display an exclamation point (“!”) and/or another notificationon optical link “13/QPSK-500” between NE-1 and NE-4 to indicate that theconnection point on NE-1 is configured for one optical link type (e.g.,“QPSK-500”), and the connection point on NE-4 is configured for adifferent optical link type (e.g., “3QAM-375”).

Additionally, or alternatively, OLAE 1255 may provide an indication ofan optical viability problem associated with an optical link. An opticalviability problem may indicate that an optical link cannot transmit asignal across a route without loss of data integrity due to errors,light degradation, etc. As illustrated, OLAE 1255 may display anexclamation point (“!”) or another notification on optical link“13/QPSK-500” between NE-1 and NE-4 to indicate that optical link 13 isnot optically viable for a particular data transmission between NE-1 andNE-4.

Cross-connect alert element (“CCAE”) 1260 may provide an indication ofan alert (e.g., a problem, an issue, a warning, a notification, etc.)associated with a cross-connect (e.g., a connection point, an add/droppoint, a termination point, etc.). For example, CCAE 1260 may provide anindication that an optical link is not connected to a cross-connect(e.g., is not being added, dropped, or routed by a node). Additionally,or alternatively, CCAE 1260 may indicate that a cross-connect and/or acomponent has not been installed, properly configured, and/orprovisioned. As illustrated, CCAE 1260 may display a question mark (“?”)and/or another notification at a cross-connect location on NE-1 toindicate that a transmission associated with optical link 13 is notbeing routed, added, or dropped by NE-1.

In some implementations, elements 1250-1260 may display a component in aparticular manner to indicate a severity of a problem associated withthe component. For example, elements 1250-1260 may display a componentusing a particular color (e.g., red, orange, yellow, green, etc.) basedon a severity level associated an alert. Additionally, or alternatively,elements 1250-1260 may provide a mechanism (e.g., a clickable element, abutton, a link, etc.) that allows a user to indicate a desire to viewalert information associated with an alert, as discussed herein.

FIG. 12C is a diagram of an example element 1200 of a user interfacethat displays optical network information. Element 1200 may be displayedby UI 700 (e.g., by optical switching view element 1105). Element 1200may include route detail view element 1115, as discussed herein inconnection with FIG. 11. Additionally, or alternatively, element 1200may include an optical link physical view 1270. Additionally, oralternatively, element 1200 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 12C.

Optical link physical view 1270 may display a physical representation ofan optical link. A physical representation may display an optical linkwith respect to the spectral slices associated with the optical link.For example, an optical link may be an optical channel group (“OCG”). AnOCG may include fixed, non-contiguous, spectral slices (e.g., tennon-contiguous sets of two adjacent spectral slices). Optical linkphysical view 1270 may display a representation of ten non-contiguoussets of two adjacent spectral slices, as illustrated. In someimplementations, the representation of the ten sets of slices may bedisplayed using a size proportional to the quantity of spectral slicesincluded in each set (e.g., two slices), as illustrated.

FIG. 12D is a diagram of an example element 1200 of a user interfacethat displays optical network information. Element 1200 may be displayedby UI 700 (e.g., by optical switching view element 1105). Element 1200may include route detail view element 1115, as discussed herein inconnection with FIG. 11. Additionally, or alternatively, element 1200may include an optical link logical view 1280. Additionally, oralternatively, element 1200 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 12D.

Optical link logical view 1280 may display a logical representation ofan optical link. A logical representation may display an optical link asa single end-to-end element, rather than displaying an optical linkbased on the actual spectral slices included in the optical link. Forexample, optical link logical view 1280 displays an OCG (e.g., OCGs 9-14and 16) as an end-to-end element with connections between three nodes,rather than displaying a representation of ten non-contiguous sets ofspectral slices.

In some implementations, UI 700 may provide a mechanism (e.g., a checkbox, a button, a drop-down box, a link, a toggle, etc.) for a user toinput an indication of a desire that UI 700 display an optical linkusing a physical view or a logical view. An element of UI 700 (e.g.,route detail view element 1115) may display a physical view of anoptical link (e.g., via optical link physical view 1270) or a logicalview of an optical link (e.g., via optical link logical view 1280) basedon the user input.

FIG. 13 is a diagram of an example element 1300 of a user interface thatdisplays optical network information. Element 1300 may be displayed byUI 700. Element 1300 may include tab element 715, view selection element820, route selection element 825, option element 830, and an FRUconnectivity view element 1305. Additionally, or alternatively, element1300 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 13.

FRU connectivity view element 1305 may be displayed by graphical element710. In some implementations, FRU connectivity view element 1305 may bedisplayed based on user selection of a tab element 715 corresponding toFRU connectivity view element 1305, and/or based on user input via userinput element 705 (e.g., view selection element 820, route selectionelement 825, and/or option element 830).

FRU connectivity view element 1305 may display a representation of NEs250, a representation of optical links between NEs 250, and/orinformation associated with the represented NEs 250 and/or therepresented optical links. FRU connectivity view element 1305 maydisplay these representations based on user input (e.g., via user inputelement 705).

View selection element 820 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) for a user to input aview type. User input of a view type may cause UI 700 and/or FRUconnectivity view element 1305 to display information based on theuser-input view type.

Route selection element 825 may provide a mechanism (e.g., a drop-downbox, a text box, a button, a menu, a link, etc.) that allows a user toinput an optical route, an optical link, and/or NE 250 to be displayedby FRU connectivity view element 1305. The user may input an opticalroute identifier, a set of NEs 250, a set of optical links, and/or anyother information that identifies an optical route, a set of NEs 250,and/or a set of optical links. In some implementations, FRU connectivityview element 1305 may display the optical route, the set of NEs 250,and/or the set of optical links based on the user input.

For example, in FIG. 13, a user has selected (via route element 825) anoptical route that connects node 1 to node 8 (e.g., NE-1 through NE-8).FRU connectivity view element 1305 may display a representation of theselected optical route. For example, FRU connectivity view element 1305may display a representation of nodes 1 through 8. Additionally, oralternatively, FRU connectivity view element 1305 may displayinformation associated with a displayed node. In some implementations,FRU connectivity view element 1305 may provide a scroll bar that may beused to display a portion of the selected optical route (e.g., node 2 ofnodes 1 through 8, as illustrated).

Option element 830 may provide a mechanism (e.g., a button, a check box,a drop-down box, a menu, etc.) that allows a user to input displayoptions, as discussed herein in connection with FIG. 8.

FIG. 14A is a diagram of an example element 1400 of a user interfacethat displays optical network information. Element 1400 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1400may include component information elements 1402-1428 (hereinafterreferred to collectively as “CIEs,” and individually as “CIE”).Additionally, or alternatively, element 1400 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 14A.

Element 1400 may represent an optical amplifier, such as an erbium dopedfiber amplifier (“EDFA”), a Raman amplifier (“RA”), an inline amplifiermodule (“TAM”) and/or an inline Raman module (“IRM”). Element 1400 maybe displayed based on user input that identifies an optical component(e.g., a node, an NE 250, and/or a component of a node and/or NE 250) todisplay (e.g., via user input element 705). For example, FIG. 14A mayrepresent two IAMs.

Element 1400 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, FIG. 14A may represent elements that are displayedwhen a user has input a data channel view (e.g., BAND), a combinedcontrol channel and data channel view (e.g., OTS), and/or a combineddata channel and optical link termination view (e.g., BAND/OL).

CIE 1402 may display information that identifies a displayed component(e.g., an IAM) using an identifier (e.g., a number, a label, text,etc.). For example, CIE 1402 may display “2-A-1” to identify a displayedIAM, as illustrated.

CIE 1404 may display information that identifies an equipment type(e.g., a type of IAM) associated with a displayed component. Anequipment type may include a type of component (e.g., optical amplifier,IAM, IRM, etc.), a version number, a model number, a vendor and/orprovider, etc. For example, CIE 1404 may display “IAM-B-ECXH1” toidentify the equipment type of a displayed IAM, as illustrated.

CIE 1406 may display information that identifies an operating modeassociated with a displayed component. An operating mode may specifyinformation to be transmitted by a component. For example, an operatingmode may specify that only information carried on a data channel shouldbe transmitted by the component, only information carried on a controlchannel should be transmitted by the component, and/or informationcarried on both a data channel and a control channel should betransmitted by the component.

CIE 1408 may display information that identifies a service stateassociated with a displayed component. A service state may includein-service (e.g., a component is working properly) or out-of-service(e.g., a component is not working properly). Additionally, oralternatively, CIE 1408 may display an alert (e.g., a warning, an issue,a problem, a notification, etc.) associated with a displayed component.CIE 1408 may display different identifiers (e.g., symbols, labels,images, text, colors, etc.) to represent different service states. Forexample, CIE 1408 may display a check mark (e.g., in green) to representthat IAM 2-A-1 is in-service, as illustrated.

CIE 1410 may display information that identifies an administrative stateassociated with a displayed component. An administrative state mayinclude locked or unlocked. A locked administrative state may take acomponent out of service, and may allow a user to change a configurationand/or a parameter associated with a component. An unlockedadministrative state may prevent a user from changing one or moreparameters and/or configurations associated with a component. In someimplementations, a component may be in-service only when unlocked. CIE1410 may display different identifiers (e.g., symbols, labels, text,images, colors, etc.) to represent different administrative states. Forexample, CIE 1410 may display an unlocked padlock to represent that IAM2-A-1 is in an unlocked administrative state.

CIE 1412 may display information that identifies a parameter associatedwith a displayed component. A parameter may include, for example, a gainparameter, a span loss parameter, a power parameter, an addressparameter, and/or any other parameter associated with a component. Again parameter may include CG, TG, and/or RG associated with acomponent, as discussed herein in connection with FIG. 10A.Additionally, or alternatively, a gain parameter may include a gain tiltoffset (“GTO”). A gain tilt offset may correct a gain tilt in a signaldue to signal amplification (e.g., a distortion of the gain spectrum inan EDFA caused by an unexpected change in the power of input signalsentering the EDFA).

CIE 1414 may display adjustment information associated with a displayedcomponent. Adjustment information may include a date and/or time thatone or more parameters (e.g., TG, GTO, etc.) associated with a componentwere last adjusted. In some implementations, a parameter may beautomatically adjusted based on an algorithm, a componentcharacteristic, and/or a signal characteristic. Adjustment informationmay include a date and/or time of a last automatic update. Additionally,or alternatively, a parameter may be manually adjusted. Adjustmentinformation may include a date and/or time of a last manual update.

CIEs 1416 and 1418 may provide a representation of a component port. Acomponent port may be a data channel port (e.g., a BAND port), a controlchannel port (e.g., an OSC port), and/or a combined data channel portand control channel port (e.g., an OTS port). For example, CIE 1416 mayprovide a representation of an OTS port where an optical fiber connectsto an IAM or IRM (e.g., IAM 2-A-1 and/or IAM 3-A-1, as illustrated). Asanother example, CIE 1418 may provide a representation of a BAND portwhere an IAM or IRM connects to an FRM.

CIE 1420 may provide a representation of an attenuator that attenuates asignal being received from a fiber and being transmitted to a component(e.g., an IAM or an IRM). In some implementations, CIE 1420 may providean indication of an attenuation level associated with the displayedcomponent.

CIE 1422 may provide a representation of an attenuator that attenuates asignal being received from a component (e.g., an IAM or an IRM), andbeing transmitted to a fiber. In some implementations, CIE 1422 mayprovide an indication of an attenuation level associated with thedisplayed component.

CIE 1424 may provide a representation of an amplification typeassociated with a component. An amplification type may be DFA, EDFA,Raman (e.g., co-propagating or counter-propagating), and/or any othertype of amplification and/or combination of amplification types, asdiscussed herein in connection with FIG. 9A. Additionally, oralternatively, CIE 1424 may provide a representation of an amplificationdirection, as discussed herein in connection with FIG. 9A. For example,CIE 1424 may represent a two stage EDFA by displaying two triangles, asillustrated.

CIEs 1426 and 1428 may provide a representation of a power parametersassociated with a component. A power parameter may include OPR, OPT, PO,and/or another power parameter, as discussed herein in connection withFIG. 10A. For example, CIE 1426 may indicate an OPR of “3.0,” and CIE1428 may indicate an OPT of “4.0.” In some implementations, CIE 1426and/or CIE 1428 may indicate an OPR and/or OPT of “N/A” when it is notpossible to determine the OPR and/or OPT value.

FIG. 14B is a diagram of an example element 1400 of a user interfacethat displays optical network information. Element 1400 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1400may include CIEs 1402-1428, as discussed herein. Additionally, oralternatively, element 1400 may include CIEs 1430-1436. Additionally, oralternatively, element 1400 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 14B.

Element 1400 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, FIG. 14B may represent elements that are displayedwhen a user has input a data channel view (e.g., BAND), a combinedcontrol channel and data channel view (e.g., OTS), and/or a combineddata channel and optical link termination view (e.g., BAND/OL).

CIE 1430 may display information that identifies a displayed component(e.g., an IRM), an equipment type (e.g., a type of IRM) of the displayedcomponent, an operating mode associated with the displayed component, aservice state associated with the displayed component, and/or anadministrative state associated with the displayed component. In someimplementations, CIE 1430 may include CIEs 1402-1410. For example, CIE1430 may identify an IRM as “3-A-1” with an equipment type of“IRM-B-ECXH1,” a particular operating mode, a service state ofin-service, and an administrative state of unlocked, as illustrated.

CIE 1432 may display information that identifies a power parameterassociated with a displayed component. A power parameter may include alaunch power offset (“LPO”), a point loss offset (“PLO”), an indicationof whether a parameter is being automatically adjusted on a component(e.g., “ADAPT: Enable” and “Auto PLO Adjust: Enable”), and/or otherpower parameters. LPO and/or PLO may increase or decrease an amount ofpower associated with an optical transmission. LPO and/or PLO may bedisplayed in any units of power, such as dBw, dBm, etc.

CIE 1434 may display information that identifies a gain parameterassociated with a displayed component. A gain parameter may include aCG, a TG, an RG, a GTO, and/or any other gain parameter associated witha component, as discussed herein.

CIE 1436 may provide a representation of an amplification typeassociated with a component. An amplification type may be DFA, EDFA,Raman (e.g., co-propagating or counter-propagating), and/or any othertype of amplification and/or combination of amplification types, asdiscussed herein in connection with FIG. 9A. Additionally, oralternatively, CIE 1436 may provide a representation of an amplificationdirection, as discussed herein in connection with FIG. 9A. For example,CIE 1436 may represent a two stage EDFA and counter-propagating Ramanamplification by displaying two triangles alongside an arrow pointing inthe opposite direction, as illustrated.

FIG. 14C is a diagram of an example element 1400 of a user interfacethat displays optical network information. Element 1400 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1400may include CIEs 1402-1436, as discussed herein. Additionally, oralternatively, element 1400 may include CIEs 1438 and 1440.Additionally, or alternatively, element 1400 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 14C.

Element 1400 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). FIG. 14C may represent an IAM or IRM where a user has input acontrol channel view (e.g., OSC).

CIE 1438 may display information that identifies an address parameter ofa control channel (e.g., an optical supervisory channel) associated witha displayed component. For example, CIE 1438 may identify an internetprotocol (“IP”) address and/or a subnet mask address associated with acontrol channel on the displayed component.

Additionally, or alternatively CIE 1438 may display information thatidentifies a control parameter associated with a displayed component.For example, CIE 1438 may display information that identifies a laserbias current (“LBC”) associated with an optical transmission via thedisplayed component.

CIE 1440 may provide a representation of a port associated with acomponent. For example, CIE 1440 may provide a representation of an OSCport where a fiber and/or optical link connects to a control module.

FIG. 15 is a diagram of an example element 1500 of a user interface thatdisplays optical network information. Element 1500 may be displayed byUI 700 (e.g., by FRU connectivity view element 1305). Element 1500 mayinclude CIEs 1402-1436 (not labeled in FIG. 15), as discussed herein.Additionally, or alternatively, element 1500 may include CIEs 1502-1522.Additionally, or alternatively, element 1500 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 15.

Element 1500 may represent an FRM capable of receiving an optical signal(e.g., from a fiber and/or an optical network component) andtransmitting the optical signal (e.g. to a fiber and/or an opticalnetwork component). Element 1500 may be displayed based on user inputthat identifies an optical component to display (e.g., via user inputelement 705). For example, FIG. 15 may represent two FRMs on a node.

Element 1500 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, elements 1500 may represent elements that aredisplayed when a user has input a data channel view (e.g., BAND), acombined control channel and data channel view (e.g., OTS), and/or acombined data channel and optical link termination view (e.g., BAND/OL).

CIE 1502 may display information that identifies a displayed component(e.g., an FRM), an equipment type (e.g., a type of FRM) of the displayedcomponent, an operating mode associated with the displayed component, aservice state associated with the displayed component, and/or anadministrative state associated with the displayed component. In someimplementations, CIE 1502 may include CIEs 1402-1410 and/or 1430. Forexample, CIE 1502 may identify an FRM as “2-A-4” with an equipment typeof “FRM-9D-8-EC,” a service state of in-service, and an administrativestate of unlocked, as illustrated.

CIE 1504 may display information that identifies a power parameterand/or another parameter associated with a displayed component. In someimplementations, CIE 1504 may include CIEs 1412, 1414, 143, and/or 1434.A power parameter may include an LPO, a PLO, an indication of whetherparameters are being automatically adjusted on a component (e.g.,“ADAPT: Enable,” “Auto PLO Adjust: Enable,” and/or “PCL: Enable”),and/or other power parameters.

CIE 1506 may provide a representation of an amplification typeassociated with a component. An amplification type may be DFA, EDFA,Raman (e.g., co-propagating or counter-propagating), and/or any othertype of amplification and/or combination of amplification types, asdiscussed herein in connection with FIG. 9A. Additionally, oralternatively, CIE 1506 may provide a representation of an amplificationdirection, as discussed herein in connection with FIG. 9A. For example,CIE 1506 may represent single stage EDFA by displaying one triangle, asillustrated.

CIE 1508 may provide a representation of a power parameter associatedwith a component. A power parameter may include OPR, OPT, PO, and/orother power parameters, as discussed herein in connection with FIG. 10A.For example, CIE 1508 may indicate an OPR of “3.0” received at adisplayed FRM, and an OPT of “4.0” transmitted by a displayed FRM. Insome implementations, CIE 1508 may indicate an OPR and/or OPT of “N/A”when it is not possible to determine the OPR and/or OPT value.

CIE 1510 may provide a representation of a port associated with acomponent. In some implementations, CIE 1510 may include CIEs 1416and/or 1418. Additionally, or alternatively, CIE 1510 may represent anFRM line port (e.g., a connection point on an FRM for a data channel).An FRM may de-multiplex signals received from a data channel andtransmit the de-multiplexed signals to different system ports.

CIE 1512 may provide a representation of a port associated with acomponent. For example, CIE 1512 may represent a system port on an FRMand/or on a node. A system port may be a location where an opticalsignal is transmitted to and/or received from another component. In someimplementations, CIE 1512 may provide a representation of a powerparameter associated with a port (e.g., OPR at a port, OPT at a port,etc.).

CIE 1514 may display information that identifies a port (e.g., a systemport). For example, a system port may be identified as “S5,” asillustrated. Additionally, or alternatively, CIE 1514 may use adifferent identifier (e.g., text, an image, a symbol, etc.) to identifya port.

CIE 1516 may provide a representation of whether a port is connectedanother port and/or component. For example, CIE 1516 may display a lineto indicate that a port is connected to another component, and may notdisplay a line to indicate that a port is not connected to anothercomponent. Additionally, or alternatively, CIE 1516 may use a differentidentifier (e.g., text, an image, a symbol, etc.) to identify whether aport is connected to another component.

CIE 1518 may provide a representation of an add/drop location for anoptical transmission. For example, CIE 1518 may display “AD” to indicatethat an optical transmission is added or dropped at port S3, asillustrated. Additionally, or alternatively, CIE 1518 may use adifferent identifier (e.g., text, an image, a symbol, etc.) to indicatethat an optical transmission is added or dropped at a port.

CIE 1520 may provide a representation of an optical transmission betweendisplayed ports. For example, CIE 1520 may display a line connecting twoports when an optical transmission has been allocated and/or is beingtransmitted between the two ports (e.g., port S9 on FRM 2-A-4 and portS9 on FRM 3-A-4, as illustrated).

CIE 1522 may provide a representation of an optical transmission betweena displayed component and a component that is not displayed. Forexample, CIE 1522 may display a line and/or an “E” to indicate that anoptical transmission has been allocated and/or is being transmittedbetween a displayed port (e.g., port S10 on FRM 3-A-4) and a port thatis not displayed (e.g., the optical transmission has been expressed in adirection other than between the displayed FRMs).

FIG. 16 is a diagram of an example element 1600 of a user interface thatdisplays optical network information. Element 1600 may be displayed byUI 700 (e.g., by FRU connectivity view element 1305). Element 1600 mayinclude CIEs 1602-1618. Additionally, or alternatively, element 1600 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 16.

Element 1600 may represent an OADM capable of receiving an opticalsignal (e.g., from a fiber and/or an optical network component) andtransmitting the optical signal (e.g. to a fiber and/or an opticalnetwork component). For example, element 1600 may represent an OADM witha single line port (identified in the figures as “FMM”). Element 1600may be displayed based on user input that identifies an opticalcomponent to display (e.g., via user input element 705). For example,FIG. 16 may represent an FMM connected to an FRM and asource/destination component. An FMM may be referred to as a sourcedevice or a destination device herein.

Element 1600 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, elements 1600 may be displayed when a user has inputan optical link termination view (e.g., OL), and/or a data channel andoptical link termination view (e.g., BAND/OL).

CIE 1602 may display information that identifies a displayed component(e.g., an FMM), an equipment type (e.g., a type of FMM) of the displayedcomponent, an operating mode associated with the displayed component, aservice state associated with the displayed component, and/or anadministrative state associated with the displayed component. Forexample, CIE 1602 may identify an FMM as “2-A-8” with an equipment typeof “FMM,” a service state of in-service, and an administrative state ofunlocked, as illustrated.

CIE 1604 may provide a representation of a port associated with acomponent. For example, CIE 1604 may represent a line port on an FMM. Aline port on an FMM may be a location where an optical signal istransmitted to and/or received from another component (e.g., an FRM). Insome implementations, CIE 1604 may provide a representation of a powerparameter associated with a port (e.g., OPR at a port, OPT at a port,etc.).

CIE 1606 may provide a representation of a port associated with acomponent. For example, CIE 1606 may represent an add/drop port on anFMM. An add/drop port on an FMM may be a location where an opticalsignal is transmitted to and/or received from another component (e.g.,an optical source and/or destination component, a line module, etc.). Insome implementations, CIE 1606 may provide a representation of a powerparameter associated with a port (e.g., OPR at a port, OPT at a port,etc.).

CIE 1608 may display information that identifies a port (e.g., anadd/drop port, a tributary port, etc.). For example, an add/drop portmay be identified as “T9,” as illustrated. Additionally, oralternatively, CIE 1608 may use a different identifier (e.g., text, animage, a symbol, etc.) to identify a port.

CIE 1610 may provide a representation of a line module (e.g., a sourceand/or destination component) connected to an FMM. CIE 1610 may providethe representation based on user input. For example, the providedrepresentation may include a line module associated with auser-specified optical route. A line module representation is discussedin more detail herein in connection with FIG. 18.

CIE 1612 may provide a representation of an add/drop port that isconnected to a line port (e.g., a line port that connects to an FRM),and is connected to a line module (e.g., a source/destinationcomponent). For example, CIE 1612 may display a line connecting anadd/drop port to a line port, and may display a line connecting theadd/drop port to a line module, as illustrated.

CIE 1614 may provide a representation of an add/drop port that isconnected to a line module (e.g., a source/destination component), butis not connected to a line port (e.g., a line port that connects to anFRM). For example, CIE 1614 may display a line connecting an add/dropport to a line module, and may not display a line connecting theadd/drop port to a line port, as illustrated.

CIE 1616 may provide a representation of an add/drop port that isconnected to a line port (e.g., a line port that connects to an FRM),but is not connected to a line module (e.g., a source/destinationcomponent). For example, CIE 1616 may display a line connecting anadd/drop port to a line port, and may not display a line connecting theadd/drop port to a line module (and/or may not display a line module),as illustrated.

CIE 1618 may provide a representation of an add/drop port that is notconnected to a line port (e.g., a line port that connects to an FRM),and is not connected to a line module (e.g., a source/destinationcomponent). For example, CIE 1618 may not display a line connecting anadd/drop port to a line port, and may not display a line connecting theadd/drop port to a line module (and/or may not display a line module),as illustrated.

FIG. 17 is a diagram of an example element 1700 of a user interface thatdisplays optical network information. Element 1700 may be displayed byUI 700 (e.g., by FRU connectivity view element 1305). Element 1700 mayinclude CIEs 1702-1732. Additionally, or alternatively, element 1700 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 17.

Element 1700 may represent an OADM capable of receiving an opticalsignal (e.g., from a fiber and/or an optical network component) andtransmitting the optical signal (e.g. to a fiber and/or an opticalnetwork component). For example, element 1700 may represent an OADM withmultiple line ports (identified in the figure as “FSM”). Element 1700may be displayed based on user input that identifies an opticalcomponent to display (e.g., via user input element 705). For example,FIG. 17 may represent an FSM connected to an FRM and asource/destination component. An FSM may be referred to as a sourcedevice or a destination device herein.

Element 1700 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, element 1700 may be displayed when a user has inputan optical link termination view (e.g., OL), and/or a data channel andoptical link termination view (e.g., BAND/OL).

CIE 1702 may display information that identifies a displayed component(e.g., an FSM), an equipment type (e.g., a type of FSM) of the displayedcomponent, an operating mode associated with the displayed component, aservice state associated with the displayed component, and/or anadministrative state associated with the displayed component. Forexample, CIE 1702 may identify an FSM as “2-A-8” with an equipment typeof “FSM,” a service state of in-service, and an administrative state ofunlocked, as illustrated.

CIE 1704 may provide a representation of a port associated with acomponent. For example, CIE 1704 may represent a line port on an FSM. Aline port on an FSM may be a location where an optical signal istransmitted to and/or received from another component (e.g., an FRM). Insome implementations, CIE 1704 may provide a representation of a powerparameter associated with a port (e.g., OPR at a port, OPT at a port,etc.).

CIE 1706 may display information that identifies a port (e.g., a lineport). For example, a line port may be identified as “L8,” asillustrated. Additionally, or alternatively, CIE 1706 may use adifferent identifier (e.g., text, an image, a symbol, etc.) to identifya port.

CIE 1708 may provide a representation of a port associated with acomponent. For example, CIE 1708 may represent an add/drop port on anFSM. An add/drop port on an FSM may be a location where an opticalsignal is transmitted to and/or received from another component (e.g.,an optical source and/or destination component, a line module, etc.). Insome implementations, CIE 1708 may provide a representation of a powerparameter associated with a port (e.g., OPR at a port, OPT at a port,etc.).

CIE 1710 may display information that identifies a port (e.g., anadd/drop port, a tributary port, etc.). For example, an add/drop portmay be identified as “T11,” as illustrated. Additionally, oralternatively, CIE 1710 may use a different identifier (e.g., text, animage, a symbol, etc.) to identify a port.

CIE 1712 may provide a representation of a line module (e.g., a sourceand/or destination component) connected to an FSM. CIE 1712 may providethe representation based on user input. For example, the providedrepresentation may include a line module associated with auser-specified optical route. A line module representation is discussedin more detail herein in connection with FIG. 18.

CIE 1714 may provide a representation of an add/drop port that isconnected to a line port associated with a user-specified route and/oroptical link, and is connected to a line module (e.g., asource/destination component). For example, a user may input an opticalroute associated with line port L4. CIE 1714 may display a lineconnecting add/drop port T1 to line port L4, and may display a lineconnecting add/drop port T1 to a line module, as illustrated.

CIE 1716 may provide a representation of an add/drop port that isconnected to a line port associated with a route other than auser-specified route, and is connected to a line module (e.g., asource/destination component). For example, a user may input an opticalroute associated with line port L4. CIE 1716 may display a line fromadd/drop port T2 that does not connect to line port L4 to indicate thatadd/drop port T2 is connected to a line port other than line port L4.CIE 1716 may also display a line from add/drop port T2 to indicate thatadd/drop port T2 is connected to a line module (e.g., a line extendingto the left of add/drop port T2, as illustrated).

CIE 1718 may provide a representation of an add/drop port that isconnected to a line port associated with a route other than auser-specified route, and is not connected to a line module (e.g., asource/destination component). For example, a user may input an opticalroute associated with line port L4. CIE 1718 may display a line fromadd/drop port T4 that does not connect to line port L4 to indicate thatadd/drop port T4 is connected to a line port other than line port L4.CIE 1718 may not display a line from add/drop port T4 (e.g. may notdisplay a line extending to the left of add/drop port T4, asillustrated) to indicate that add/drop port T4 is not connected to aline module.

CIE 1720 may provide a representation of an add/drop port that isconnected to a line port associated with a user-specified route, but isnot connected to a line module (e.g., a source/destination component).For example, a user may input an optical route associated with line portL4. CIE 1720 may display a line connecting add/drop port T5 to line portL4 to indicate that add/drop port T5 is connected to line port L4. CIE1720 may not display a line from add/drop port T5 (e.g. may not displaya line extending to the left of add/drop port T5, as illustrated) toindicate that add/drop port T5 is not connected to a line module.

CIE 1722 may provide a representation of an add/drop port that is notconnected to a line port, but is connected to a line module (e.g., asource/destination component). For example, CIE 1722 may not display aline from add/drop port T6 (e.g. may not display a line extending to theright of add/drop port T6, as illustrated) to indicate that add/dropport T6 is not connected to a line port. CIE 1722 may display a linefrom add/drop port T6 to indicate that add/drop port T6 is connected toa line module (e.g., a line extending to the left of add/drop port T6,as illustrated).

CIE 1724 may provide a representation of an add/drop port that is notconnected to a line port, and is not connected to a line module (e.g., asource/destination component). For example, CIE 1724 may not display aline from add/drop port T7 (e.g. may not display a line extending to theright of add/drop port T7, as illustrated) to indicate that add/dropport T7 is not connected to a line port. CIE 1724 may not display a linefrom add/drop port T7 (e.g. may not display a line extending to the leftof add/drop port T7, as illustrated) to indicate that add/drop port T7is not connected to a line module.

CIE 1726 may provide a representation of a line port, associated with auser-specified route, that is connected to an add/drop port on an FSM(e.g., one or more of add/drop ports T1-T12), and is connected to a porton another component (e.g., a port on an FRM). For example, a user mayinput an optical route associated with line port L4. CIE 1726 maydisplay a line (e.g., extending to the right, as illustrated) toindicate that line port L4 is connected to a port on an FRM. CIE 1726may also display a line connecting line port L4 to an add/drop port onthe displayed component (e.g., ports T1, T5, and T9-T12 on FSM 2-A-8, asillustrated), to indicate that line port L4 is connected to the add/dropports on the FSM.

CIE 1728 may provide a representation of a line port, not associatedwith a user-specified route, that is connected to an add/drop port onthe displayed component (e.g., ports T1-T12 on FSM 2-A-8), and isconnected to a port on another component (e.g., a port on an FRM). Forexample, a user may input an optical route associated with line port L4.CIE 1728 may display a line (e.g., extending to the right, asillustrated) to indicate that line port L6 (not specified by the user)is connected to a port on an FRM. CIE 1728 may also display a line(e.g., extending to the left, as illustrated) to indicate that line portL6 (not specified by the user) is connected to an add/drop port on theFSM (e.g., add/drop port T2, T4, and/or T8).

CIE 1730 may provide a representation of a line port, not associatedwith a user-specified route, that is connected to a port on anothercomponent (e.g., a port on an FRM), but is not connected to an add/dropport on the displayed component (e.g., ports T1-T12 on FSM 2-A-8). Forexample, a user may input an optical route associated with line port L4.CIE 1730 may display a line (e.g., extending to the right, asillustrated) to indicate that line port L2 (not specified by the user)is connected to a port on an FRM. CIE 1730 may not display a line (e.g.,may not display a line extending to the left of line port L2, asillustrated) to indicate that line port L2 (not specified by the user)is not connected to an add/drop port on the FSM.

CIE 1732 may provide a representation of a line port, not associatedwith a user-specified route, that is not connected to a port on anothercomponent (e.g., a port on an FRM), and is not connected to an add/dropport on the displayed component (e.g., ports T1-T12 on FSM 2-A-8). Forexample, a user may input an optical route associated with line port L4.CIE 1732 may not display a line (e.g., may not display a line extendingto the right of line port L1, as illustrated) to indicate that line portL1 (not specified by the user) is not connected to a port on an FRM. CIE1732 may also not display a line (e.g., may not display a line extendingto the left of line port L1, as illustrated) to indicate that line portL1 (not specified by the user) is not connected to an add/drop port onthe FSM.

FIG. 18 is a diagram of an example element 1800 of a user interface thatdisplays optical network information. Element 1800 may be displayed byUI 700 (e.g., by FRU connectivity view element 1305). Element 1800 mayinclude CIEs 1802-1806. Additionally, or alternatively, element 1800 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 18.

Element 1800 may represent a source/destination component capable ofreceiving an optical signal (e.g., from a fiber and/or an opticalnetwork component) and transmitting an optical signal (e.g. to a fiberand/or an optical network component). Element 1800 may be displayedbased on user input that identifies an optical component to display(e.g., via user input element 705).

Elements 1800 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, elements 1800 may be displayed when a user has inputan optical link termination view (e.g., OL), and/or a data channel andoptical link termination view (e.g., BAND/OL).

CIE 1802 may display information that identifies a displayed component(e.g., a source/destination component), an equipment type (e.g., a typeof source/destination component) of the displayed component, anoperating mode associated with the displayed component, a service stateassociated with the displayed component, and/or an administrative stateassociated with the displayed component. For example, CIE 1802 mayidentify a source/destination component as “1-A-1” with an equipmenttype of “AOFM-500,” a service state of in-service, and an administrativestate of unlocked, as illustrated.

CIE 1804 may display information that identifies an optical link type,an optical link identifier, and/or an optical link modulation formatassociated with a source/destination component (e.g., an optical linkcapable of being transmitted and/or received by the source/destinationcomponent). For example, CIE 1804 may identify an optical linkassociated with source/destination component 1-A-1 as super-channel 1(“SC: 1,” as illustrated), with a modulation format of “QPSK,” asillustrated.

CIE 1806 may identify a port on a source/destination component. Forexample, CIE 1806 may identify a port on a source/destination componentthat may communicate with a port on another component (e.g., an FSMand/or an FMM). In some implementations, CIE 1806 may provide arepresentation of a power parameter associated with the port (e.g., OPRat the port, OPT at the port, etc.).

FIG. 19A is a diagram of an example element 1900 of a user interfacethat displays optical network information. Element 1900 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1900may include CIEs 1905, 1925, and 1930. Additionally, or alternatively,element 1900 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 19A.

CIEs 1905, 1925, and/or 1930 may be displayed by UI 700 based on userinput of a view type (e.g., via user input element 705 and/or viewselection element 820). For example, CIEs 1905, 1925, and/or 1930 mayrepresent elements that are displayed when a user has input a datachannel view (e.g., BAND), a combined control channel and data channelview (e.g., OTS), and/or a combined data channel and optical linktermination view (e.g., BAND/OL).

CIE 1905 may display a representation of an add/drop terminal site at anode (e.g., Node 1). CIE 1905 may display an equipment type associatedwith the add/drop terminal site (e.g., DTN-X). The add/drop terminalsite may include an IAM or an IRM, connected to an FRM, as illustrated.The displayed components (e.g., IAM, IRM and/or FRM) may be associatedwith a user-specified optical route. CIE 1905 may provide an indicationof ports on the displayed components (e.g., IAM, IRM, and/or FRM) thatare connected (e.g., by displaying a line connecting the ports).

CIE 1925 may correspond to an IAM or an IRM in a view that includes adata channel (e.g., BAND, OTS, and/or BAND/OL), as discussed herein inconnection with FIGS. 14A and 14B.

CIE 1930 may correspond to an FRM, as discussed herein in connectionwith FIG. 15.

FIG. 19B is a diagram of an example element 1900 of a user interfacethat displays optical network information. Element 1900 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1900may include CIEs 1910 and 1925-1935. Additionally, or alternatively,element 1900 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 19B.

CIEs 1910 and 1925-1935 may be displayed by UI 700 based on user inputof a view type (e.g., via user input element 705 and/or view selectionelement 820). For example, CIEs 1910 and 1925-1935 may be displayed whena user has input an optical link termination view (e.g., OL), and/or adata channel and optical link termination view (e.g., BAND/OL).

CIE 1910 may display a representation of an add/drop terminal site at anode (e.g., Node 1). CIE 1910 may display an equipment type associatedwith the add/drop terminal site (e.g., DTN-X). The add/drop terminalsite may include an IAM or an IRM, connected to an FRM, which isconnected to an FSM, as illustrated. The displayed components (e.g.,IAM, IRM, FRM, and/or FSM) may be associated with a user-specifiedoptical route. CIE 1910 may provide an indication of ports on thedisplayed components (e.g., IAM, IRM, FRM, and/or FSM) that areconnected (e.g., by displaying a line connecting the ports).

CIE 1925 may correspond to an IAM or an IRM in a view that includes adata channel (e.g., BAND, OTS, and/or BAND/OL), as discussed herein inconnection with FIGS. 14A and 14B.

CIE 1930 may correspond to an FRM, as discussed herein in connectionwith FIG. 15.

CIE 1935 may correspond to an FSM, as discussed herein in connectionwith FIG. 17.

FIG. 19C is a diagram of an example element 1900 of a user interfacethat displays optical network information. Element 1900 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1900may include CIEs 1915, 1925, 1930, and 1940. Additionally, oralternatively, element 1900 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 19C.

CIEs 1915, 1925, 1930, and 1940 may be displayed by UI 700 based on userinput of a view type (e.g., via user input element 705 and/or viewselection element 820). For example, CIEs 1915, 1925, 1930, and 1940 maybe displayed when a user has input an optical link termination view(e.g., OL), and/or a data channel and optical link termination view(e.g., BAND/OL).

CIE 1915 may display a representation of an add/drop terminal site at anode (e.g., Node 1). CIE 1915 may display an equipment type associatedwith the add/drop terminal site (e.g., DTN-X). The add/drop terminalsite may include an IAM or an IRM, connected to an FRM, which isconnected to two FMMs, as illustrated. The displayed components (e.g.,IAM, IRM, FRM, and/or FMM) may be associated with a user-specifiedoptical route. CIE 1915 may provide an indication of ports on thedisplayed components (e.g., IAM, IRM, FRM, and/or FMM) that areconnected (e.g., by displaying a line connecting the ports).

CIE 1925 may correspond to an IAM or an IRM in a view that includes adata channel (e.g., BAND, OTS, and/or BAND/OL), as discussed herein inconnection with FIGS. 14A and 14B.

CIE 1930 may correspond to an FRM, as discussed herein in connectionwith FIG. 15.

CIE 1940 may correspond to an FMM, as discussed herein in connectionwith FIG. 16.

FIG. 19D is a diagram of an example element 1900 of a user interfacethat displays optical network information. Element 1900 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 1900may include CIEs 1920 and 1945. Additionally, or alternatively, element1900 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 19D.

CIEs 1920 and 1945 may be displayed by UI 700 based on user input of aview type (e.g., via user input element 705 and/or view selectionelement 820). For example, CIEs 1920 and 1945 may be displayed when auser has input a control channel view (e.g., OSC).

CIE 1920 may display a representation of an add/drop terminal site at anode (e.g., Node 3). CIE 1920 may display an equipment type associatedwith the add/drop terminal site. The add/drop terminal site may includean IAM or an IRM, as illustrated. The displayed components (e.g., IAM,IRM) may be associated with a user-specified optical route. CIE 1920 mayprovide an indication of ports on the displayed components (e.g., IAMand/or IRM) that are connected (e.g., by displaying a line connectingthe ports).

CIE 1945 may correspond to an IAM or an IRM in a control channel view(e.g., OSC), as discussed herein in connection with FIG. 14C.

FIG. 20A is a diagram of an example element 2000 of a user interfacethat displays optical network information. Element 2000 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2000may include CIEs 2010 and 2020. Additionally, or alternatively, element2000 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 20A.

CIEs 2010 and 2020 may be displayed by UI 700 based on user input of aview type (e.g., via user input element 705 and/or view selectionelement 820). For example, CIEs 2010 and 2020 may be displayed when auser has input a data channel view (e.g., OTS and/or BAND) and/or a datachannel and optical link termination view (e.g., BAND/OL).

CIE 2010 may display a representation of an optical amplifier site at anode (e.g., Node 4). CIE 2010 may display an equipment type associatedwith the optical amplifier site (e.g., OA). The optical amplifier sitemay include an IAM or an IRM. The displayed components (e.g., IAM, IRM)may be associated with a user-specified optical route. CIE 2010 mayprovide an indication of ports on the displayed components (e.g., IAMand/or IRM) that are connected (e.g., by displaying a line connectingthe ports).

CIE 2020 may correspond to an IAM or an IRM in a view that includes adata channel (e.g., BAND, OTS, and/or BAND/OL), as discussed herein inconnection with FIGS. 14A and 14B.

FIG. 20B is a diagram of an example element 2000 of a user interfacethat displays optical network information. Element 2000 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2000may include CIEs 2030 and 2040. Additionally, or alternatively, element2000 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 20B.

CIEs 2030 and 2040 may be displayed by UI 700 based on user input of aview type (e.g., via user input element 705 and/or view selectionelement 820). For example, CIEs 2030 and 2040 may be displayed when auser has input a control channel view (e.g., OSC).

CIE 2030 may display a representation of an optical amplifier site at anode (e.g., Node 2). CIE 2030 may display an equipment type associatedwith the optical amplifier site (e.g., OA). The optical amplifier sitemay include an IAM or an IRM. The displayed components (e.g., IAM, IRM)may be associated with a user-specified optical route. CIE 2030 mayprovide an indication of ports on the displayed components (e.g., IAMand/or IRM) that are connected (e.g., by displaying a line connectingthe ports).

CIE 2040 may correspond to an IAM or an IRM in a control channel view,as discussed herein in connection with FIG. 14C.

FIG. 21A is a diagram of an example element 2100 of a user interfacethat displays optical network information. Element 2100 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2100may include CIEs 2110-2130. Additionally, or alternatively, element 2100may include fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 21A.

CIEs 2110-2130 may be displayed by UI 700 based on user input of a viewtype (e.g., via user input element 705 and/or view selection element820). For example, CIEs 2110-2130 may be displayed when a user has inputa data channel view (e.g., OTS and/or BAND) and/or a data channel andoptical link termination view (e.g., BAND/OL).

CIE 2110 may display a representation of a ROADM site at a node (e.g.,Node 3). CIE 2110 may display an equipment type associated with theROADM site (e.g., DTN-X). The ROADM site may include an IAM or an IRM,and an FRM. The displayed components (e.g., IAM, IRM, and/or FRM) may beassociated with a user-specified optical route. CIE 2110 may provide anindication of ports on the displayed components (e.g., IAM, IRM, and/orFRM) that are connected (e.g., by displaying a line connecting theports).

CIE 2120 may correspond to an IAM or an IRM in a view that includes adata channel (e.g., BAND, OTS, and/or BAND/OL), as discussed herein inconnection with FIGS. 14A and 14B.

CIE 2130 may correspond to an FRM in a view that includes a data channel(e.g., BAND, OTS, and/or BAND/OL), as discussed herein in connectionwith FIG. 15.

FIG. 21B is a diagram of an example element 2100 of a user interfacethat displays optical network information. Element 2100 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2100may include CIEs 2140 and 2150. Additionally, or alternatively, element2100 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 21B.

CIEs 2140 and 2150 may be displayed by UI 700 based on user input of aview type (e.g., via user input element 705 and/or view selectionelement 820). For example, CIEs 2140 and 2150 may be displayed when auser has input a control channel view (e.g., OSC).

CIE 2140 may display a representation of a ROADM site at a node (e.g.,Node 2). CIE 2140 may display an equipment type associated with theROADM site (e.g., DTN-X). The ROADM site may include an IAM or an IRM.The displayed components (e.g., IAM, IRM) may be associated with auser-specified optical route. CIE 2140 may provide an indication ofports on the displayed components (e.g., IAM and/or IRM) that areconnected (e.g., by displaying a line connecting the ports).

CIE 2150 may correspond to an IAM or an IRM in a control channel view,as discussed herein in connection with FIG. 14C.

FIG. 22A is a diagram of an example element 2200 of a user interfacethat displays optical network information. Element 2200 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2200may include CIE 2210. Additionally, or alternatively, element 2200 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 22A.

CIE 2210 may be displayed by UI 700 based on user input of a view type(e.g., via user input element 705 and/or view selection element 820).For example, CIE 2210 may be displayed when a user has input a datachannel view (e.g., OTS and/or BAND).

CIE 2210 may display an end-to-end view of components associated with ofa user-specified route. For example, CIE 2210 may display an add/dropterminal site (e.g., Node 1, discussed herein in connection with FIG.19A), connected to a ROADM site (e.g., Node 2, discussed herein inconnection with FIG. 21A), connected to an optical amplifier site (e.g.,Node 3, discussed herein in connection with FIG. 20A), and connected toanother add/drop terminal site (e.g., Node 4, discussed herein inconnection with FIG. 19A). The end-to-end view may display differentcomponents and/or may display components differently based on auser-specified view and/or a user-specified route. CIE 2210 may providean indication of ports on the displayed components (e.g., IAM, IRM, FRM,FMM, and/or FSM) that are connected (e.g., by displaying a lineconnecting the ports).

FIG. 22B is a diagram of an example element 2200 of a user interfacethat displays optical network information. Element 2200 may be displayedby UI 700 (e.g., by FRU connectivity view element 1305). Element 2200may include CIE 2220. Additionally, or alternatively, element 2200 mayinclude fewer elements, additional elements, different elements, ordifferently arranged elements than those illustrated in FIG. 22A.

CIE 2220 may be displayed by UI 700 based on user input of a view type(e.g., via user input element 705 and/or view selection element 820).For example, CIE 2220 may be displayed when a user has input a controlchannel view (e.g., OSC).

CIE 2220 may display an end-to-end view of components associated with auser-specified route. For example, CIE 2220 may display an add/dropterminal site (e.g., Node 1, discussed herein in connection with FIG.19D), connected to a ROADM site (e.g., Node 2, discussed herein inconnection with FIG. 21B), connected to an optical amplifier site (e.g.,Node 3, discussed herein in connection with FIG. 20B), and connected toanother add/drop terminal site (e.g., Node 4, discussed herein inconnection with FIG. 19D). The end-to-end view may display differentcomponents and/or may display components differently based on auser-specified view and/or a user-specified route. CIE 2220 may providean indication of ports on the displayed components (e.g., IAM and/orIRM) that are connected (e.g., by displaying a line connecting theports).

FIG. 23 is a diagram of an example element 2300 of a user interface thatdisplays optical network information. Element 2300 may be displayed byUI 700. Element 2300 may include tab element 725, tab element 730, and apower evolution table element 2305. Additionally, or alternatively,element 2300 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 23.

Power evolution table element (“PETE”) 2305 may be displayed based onuser selection of a tab element 725 and/or a tab element 730corresponding to PETE 2305, and/or based on user input via user inputelement 705. In some implementations, user selection of a tab element725 may cause different tabs to be displayed by tab element 730.

PETE 2305 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical route). In some implementations, PETE2305 may display information (e.g., a power parameter) associated with aset of nodes on an optical route that is associated with auser-specified optical link. For example, the displayed information maybe based on user selection of an element displayed by graphical element710.

In some implementations, PETE 2305 may display power characteristics(e.g., OPT, OPR, PO) for optical links from a source node to adestination node on a user-specified route, which may include one ormore intermediate nodes that connect the source node to the destinationnode. PETE 2305 may show or hide one or more power characteristics basedon user input. Additionally, or alternatively, PETE 2305 may show orhide information (e.g., power characteristics) associated with one ormore nodes and/or NEs 250 based on user input (e.g., user input of a setof optical links associated with the nodes).

For example, PETE 2305 may display OPT and/or OPR for an optical link(identified in the figure as “SCHCTP”) and/or an optical link group(identified in the figure as “SCGPTP”) on a source/destination component(e.g., an “AOFX/SOFX,” an “FMM,” and/or an “FSM”) at a source nodeand/or a destination node. Additionally, or alternatively, PETE 2305 maydisplay OPT, OPR, and/or PO for an optical link on an FRM and/or an FRMport at a source node and/or a destination node. Additionally, oralternatively, PETE 2305 may display OPT, OPR and/or PO for an opticallink on an FRM and/or an FRM port at an intermediate node (e.g., in oneor both transmission directions).

FIG. 24 is a diagram of an example data structure 2400 that storesinformation associated with an optical network. Data structure 2400 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 2400 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 2400may be displayed by UI 700 (e.g., by PETE 2305). For example, datastructure 2400 may be represented as a table on UI 700 (e.g., by chartelement 720).

Data structure 2400 may include a collection of fields 2402-2446. Datastructure 2400 includes fields 2402-2446 for explanatory purposes. Inpractice, data structure 2400 may include additional fields, fewerfields, different fields, or differently arranged fields than aredescribed with respect to data structure 2400.

Field 2402 may store information that identifies an optical link (e.g.,a super-channel). For example, field 2402 may identify an optical linkusing a number and/or another identifier (e.g., “1,” “SCH 1,” “6a,”etc.). Information associated with a set of optical links stored by datastructure 2400 may be displayed by UI 700 based on user input (e.g.,user input of an optical route that includes the set of optical links).

Field 2404 may store information that identifies an optical link typeassociated with the optical link identified by field 2402. For example,field 2404 may identify an optical link type using a modulation formatand/or a bandwidth associated with an optical link.

Field 2406 may store information that identifies a route directionassociated with the optical link identified by field 2402. In thefigures, a route direction may be identified by “W” or “West” for onedirection, or “E” or “East” for another direction. In someimplementations, nodes displayed on the left of UI 700 may be labeledwith a “West” direction, and nodes displayed on the right of UI 700 maybe labeled with an “East” direction. Fields 2408-2446 may be displayedin a different order depending on the route direction associated withthe optical link identified by field 2402. For example, fields 2408-2432may be associated with a west node, and fields 2434-2446 may beassociated with an east node.

Field 2408 may store information that identifies a node, on one end ofan optical route, associated with the optical link identified by field2402. For example, the node identified by field 2408 may be a sourcenode. A source node may include a node that transmits an optical signal.For example, field 2408 may identify a source node using a nodeidentifier (e.g., “Node-1”).

Field 2410 may store information that identifies a source componentand/or a source component port associated with the optical linkidentified by field 2402. For example, a source node and/or port may beassociated with the node identified by field 2408. A source componentmay include a component that transmits an optical signal. For example,field 2410 may identify a source component using a component and/or portidentifier (e.g., “1-A-3-L1-1”).

Field 2412 may store information that identifies an encoding modeassociated with the optical link identified by field 2402. An encodingmode may identify how a signal is encoded for transmission to anothercomponent.

Field 2414 may store information that identifies a channel group modeassociated with the optical link identified by field 2402. A channelgroup mode may identify a quantity of optical links (e.g., a channel, ora super-channel) that are multiplexed together to form another opticallink (e.g., a super-channel, or a super-channel group). For example, achannel group mode may include “single” (e.g., one channel persuper-channel), “dual” (e.g., two channels per super-channel), or “all”(e.g., ten channels per super-channel). Additionally, or alternatively,a channel group mode may identify any quantity of channels multiplexedtogether to form super-channels, and/or any quantity of super-channelsmultiplexed together to form super-channel groups.

Field 2416 may store information that identifies a bandwidth associatedwith the optical link identified by field 2402. For example, a bandwidthmay be represented in gigahertz (GHz), which may represent an amount ofbandwidth allocated to an optical link for transmission of an opticalsignal.

Fields 2418 and 2420 may store information that identifies an OPTassociated with the optical link identified by field 2402 when theoptical link is transmitted from the source component identified byfield 2410. In some implementations, field 2418 may identify an OPT atwhich the source component transmits the optical link identified byfield 2402 when the optical link is not multiplexed together with otheroptical links (e.g., when the optical link is a single channel, or asingle super-channel). Additionally, or alternatively, field 2420 mayidentify an OPT at which the source component transmits the optical linkidentified by field 2402 when the optical link is multiplexed togetherwith another optical link (e.g., to form a super-channel of multiplechannels, or to form a super-channel group of multiple super-channels).

Field 2422 may store information that identifies an OPR associated withthe optical link identified by field 2402 when the optical link isreceived by a source FMM or FSM (e.g., identified by field 2424). Insome implementations, the optical link may be part of an optical linkgroup (e.g., a super-channel group) when received by a source FMM orFSM.

Field 2424 may store information that identifies a source FMM, FSM, FMMport, and/or FSM port associated with the optical link identified byfield 2402. For example, a source FMM, FSM, FMM port, and/or FSM portmay be associated with the node identified by field 2408. For example,field 2424 may identify a source FMM or FSM using a component and/orport identifier (e.g., “3-A-1-T1”).

Field 2426 may store information that identifies a PO associated with asource FRM line port associated with the optical link identified byfield 2402. For example, a PO may be applied to a super-channel and/orsuper-channel group received at a port (e.g., the port identified byfield 2424).

Field 2428 may store information that identifies a source FRM and/or FRMport associated with the optical link identified by field 2402. Forexample, a source FRM and/or FRM port may be associated with the nodeidentified by field 2408. For example, field 2428 may identify a sourceFRM using a component and/or port identifier (e.g., “3-A-5-L1-1”).

Field 2430 may store information that identifies a PO associated withthe optical link identified by field 2402 when the optical link isprocessed by a source FRM. For example, a PO may be applied to a channeland/or super-channel that has been de-multiplexed for transmission(e.g., via the port identified by field 2428).

Field 2432 may store information that identifies an OPT associated withthe optical link identified by field 2402 when the optical link istransmitted from the source FRM associated with the optical link (e.g.,identified by field 2428).

Field 2434 may store information that identifies a node, on one end ofan optical route, associated with the optical link identified by field2402. For example, the node identified by field 2434 may be adestination node. A destination node may include a node that receives anoptical signal. For example, field 2434 may identify a destination nodeusing a node identifier (e.g., “Node-8”).

Field 2436 may store information that identifies an OPR associated withthe optical link identified by field 2402 when the optical link isreceived by the destination FRM associated with the optical link (e.g.,identified by field 2440).

Field 2438 may store information that identifies a destination FRMand/or FRM port associated with the optical link identified by field2402. For example, field 2438 may identify a destination FRM using acomponent and/or port identifier (e.g., “3-A-5-L1-1”).

Field 2440 may store information that identifies a destination componentand/or a destination component port associated with the optical linkidentified by field 2402. A destination component may include acomponent that receives an optical signal. For example, field 2440 mayidentify a destination component using a component and/or portidentifier (e.g., “1-A-3-L1”).

Field 2442 may store information that identifies an OPR associated withthe optical link identified by field 2402 when the optical link isreceived by the destination component associated with the optical link.

Field 2444 may store information that identifies apre-forward-error-correction bit error rate (“Pre-FEC BER”) and/or apost-forward-error correction bit error rate (“Post-FEC BER”) associatedwith the optical link identified by field 2402. In some implementations,multiple optical links may be multiplexed together to form an opticallink group. Field 2444 may identify a minimum and/or maximum pre-FEC BERassociated with one of the optical links in the optical link group.Similarly, field 2444 may identify a minimum and/or maximum post-FEC BERassociated with one of the optical links in the optical link group.

Field 2446 may store information that identifies a signal quality (e.g.,“Q-Val”) associated with the optical link identified by field 2402. Asignal quality may include a signal-to-noise ratio, a signalinterference to noise ratio (SINR), and/or another quality parameter. Insome implementations, field 2446 may identify a signal qualityassociated with a single optical link and/or an optical link group.Additionally, or alternatively, field 2446 may identify a minimum and/ormaximum signal quality associated with one of the optical links in theoptical link group.

Information for a single optical link may be conceptually represented asa row in data structure 2400. For example, the first row in datastructure 2400 may correspond to a super-channel identified as “1,” witha super-channel type of “PM-QPSK-500,” (e.g., a modulation format ofQPSK and a bandwidth of 500 GHz), and a direction of West to East (e.g.,Node-1 may be displayed on the left of UI 700). A source node associatedwith super-channel 1 may have a node name of “Node-1,” and may beassociated with a source component and/or port identified as“1-A-3-L1-1.” Super-channel 1 may have an encoding mode of “BC,” achannel group mode of “All,” and a spectral bandwidth of “250 GHz”(e.g., two super-channels are multiplexed together to give asuper-channel group a bandwidth of 500 GHz). Super-channel 1 may betransmitted from source component 1-A-3-L1-1 with a power level (OPT) of“−7.” Super-channel 1 may be included in a super-channel group, whichmay be transmitted from source component 1-A-3-L1-1 with a power level(OPT) of “−7.” Super-channel 1 may be received by FMM/FSM “3-A-1-T1”with an OPR of “−7.” FMM/FSM “3-A-1-T1” may apply a PO of −2, tosuper-channel 1, which may be transmitted to FRM “3-A-5-L1-1.” FRM“3-A-5-L1-1” may transmit super-channel 1 with a power offset of “−1”and an OPT of “−9.” Super-channel 1 may be received at a destinationnode identified as “Node-8,” and an FRM identified as “3-A-5-L1-1” withan OPR of “−7.” Super-channel 1 may then be received by destinationcomponent “1-A-3-L1” with an OPR of “−3.” Super-channel 1 may have apre-FEC BER and post-FEC BER of “9E-12,” and a signal quality of“16.55.”

FIG. 25 is a diagram of an example data structure 2500 that storesinformation associated with an optical network. Data structure 2500 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 2500 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 2500may be displayed by UI 700 (e.g., by PETE 2305). For example, datastructure 2500 may be represented as a table on UI 700 (e.g., by chartelement 720).

Data structure 2500 may include a collection of fields 2502-2536. Datastructure 2500 includes fields 2502-2536 for explanatory purposes. Inpractice, data structure 2500 may include additional fields, fewerfields, different fields, or differently arranged fields than aredescribed with respect to data structure 2500.

Field 2502 may store information that identifies a first node in a setof nodes associated with a user-specified optical route. For example,field 2502 may identify a first node using a number and/or anotheridentifier (e.g., “Node-1”). Information associated with a set of firstnodes stored by data structure 2500 may be displayed by UI 700 based onuser input (e.g., user input of an optical link associated with the setof first nodes).

Field 2504 may store information that identifies a first FRM and/or afirst FRM port associated with the first node identified by field 2502.For example, field 2504 may identify a first FRM using a componentand/or port identifier (e.g., “3-A-4-L1-1”).

Field 2506 may store information that identifies an OPR associated withthe first FRM identified by field 2504. For example, field 2506 maystore information that identifies an OPR with which the FRM identifiedby field 2504 receives a user-specified optical link.

Field 2508 may store information that identifies an update date and/ortime associated with the OPR identified by field 2506. For example,field 2508 may identify the last time the OPR identified by field 2506was measured, or the last time a power adjustment associated with theOPR identified by field 2506 was made.

Field 2510 may store information that identifies an LPO associated withthe FRM identified by field 2504 or field 2512. For example, field 2510may store information that identifies an LPO that the FRM identified byfield 2504 and/or 2512 applies to a user-specified optical link.

Field 2512 may store information that identifies a second FRM and/or asecond FRM port associated with the first node identified by field 2502.For example, field 2512 may identify a second FRM using a componentand/or port identifier (e.g., “4-A-4-L1-1”). In some implementations,the first FRM may be an FRM that receives an optical link signal at thefirst node, and the second FRM may be an FRM that transmits the opticallink signal from the first node.

Field 2514 may store information that identifies a PO associated withthe second FRM identified by field 2512. For example, field 2514 maystore information that identifies a PO the FRM identified by field 2512applies to a user-specified optical link.

Field 2516 may store information that identifies an update date and/ortime associated with the OPT identified by field 2518. For example,field 2516 may identify the last time the OPT identified by field 2518was measured, or the last time a power adjustment associated with theOPT identified by field 2518 was made.

Field 2518 may store information that identifies an OPT associated withthe second FRM identified by field 2512. For example, field 2518 maystore information that identifies an OPT with which the FRM identifiedby field 2512 transmits a user-specified optical link.

Field 2520 may store information that identifies a second node in a setof nodes associated with a user-specified optical route. For example,field 2520 may identify a second node using a number and/or anotheridentifier (e.g., “Node-1”). In some implementations, the first node(e.g., Node-1) may transmit a signal to the second node (e.g., Node-2).Data structure 2500 may display the entire user-specified optical route.A particular node may be displayed in both field 2502 and field 2520(although not in the same row).

Field 2522 may store information that identifies a first FRM and/or afirst FRM port associated with the second node identified by field 2520.For example, field 2522 may identify a first FRM using a componentand/or port identifier (e.g., “3-A-4-L1-1”).

Field 2524 may store information that identifies an OPR associated withthe first FRM identified by field 2522. For example, field 2524 maystore information that identifies an OPR with which the FRM identifiedby field 2522 receives a user-specified optical link.

Field 2526 may store information that identifies an update date and/ortime associated with the OPR identified by field 2524. For example,field 2526 may identify the last time the OPR identified by field 2524was measured, or the last time a power adjustment associated with theOPR identified by field 2524 was made.

Field 2528 may store information that identifies an LPO associated withthe FRM identified by field 2522 or field 2530. For example, field 2528may store information that identifies an LPO that the FRM identified byfield 2522 and/or field 2530 applies to a user-specified optical link.

Field 2530 may store information that identifies a second FRM and/or asecond FRM port associated with the second node identified by field2520. For example, field 2530 may identify a second FRM using acomponent and/or port identifier (e.g., “4-A-4-L1-1”). In someimplementations, the first FRM may be an FRM that receives an opticallink signal at the second node, and the second FRM may be an FRM thattransmits the optical link signal from the second node.

Field 2532 may store information that identifies a PO associated withthe second FRM identified by field 2530. For example, field 2532 maystore information that identifies a PO that the FRM identified by field2530 applies to a user-specified optical link.

Field 2534 may store information that identifies an update date and/ortime associated with the OPT identified by field 2536. For example,field 2534 may identify the last time the OPT identified by field 2536was measured, or the last time a power adjustment associated with theOPT identified by field 2536 was made.

Field 2536 may store information that identifies an OPT associated withthe second FRM identified by field 2530. For example, field 2536 maystore information that identifies an OPT with which the FRM identifiedby field 2530 transmits a user-specified optical link.

FIG. 26 is a diagram of an example element 2600 of a user interface thatdisplays optical network information. Element 2600 may be displayed byUI 700 (e.g., by FRU connectivity view element 1305). Element 2600 mayinclude a directional view 2610, a directional view 2620, and an alertelement 2630. Additionally, or alternatively, element 2600 may includefewer elements, additional elements, different elements, or differentlyarranged elements than those illustrated in FIG. 26.

UI 700 may display information stored by data structure 2400 and/or 2500using different directional views. For example, directional view 2610may display data structure fields in one direction (e.g., west to east,or W→E, as illustrated), and directional view 2620 may display datastructure fields in another direction (e.g., east to west, or E→W, asillustrated). UI 700 may display information stored by data structure2400 and/or 2500 using different directional views based on user input(e.g., via user input element 705 and/or option element 830).

Alert element 2630 may provide an indication of a problem associatedwith an optical route, an optical link, an NE 250, etc., associated witha field of data structure 2400 and/or 2500. Alert element 2630 maydisplay an alert based on a severity level associated with the alert, asdescribed elsewhere herein. Additionally, or alternatively, alertelement 2630 may provide a mechanism (e.g., a clickable element, abutton, a link, etc.) that allows a user to indicate a desire to viewalert information associated with an alert, as discussed herein.

FIG. 27 is a diagram of an example element 2700 of a user interface thatdisplays optical network information. Element 2700 may be displayed byUI 700. Element 2700 may include tab element 725, tab element 730, and aband cross-section element 2705. Additionally, or alternatively, element2700 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 27.

Band cross-section element (“BCSE”) 2705 may be displayed based on userselection of a tab element 725 and/or a tab element 730 corresponding toBCSE 2705, and/or based on user input via user input element 705. Insome implementations, user selection of a tab element 725 may causedifferent tabs to be displayed by tab element 730.

BCSE 2705 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical route). In some implementations, BCSE2705 may display information (e.g., a power parameter) associated with aset of optical links on a set of user-specified nodes. For example, thedisplayed information may be based on user selection of an elementdisplayed by graphical element 710.

In some implementations, BCSE 2705 may display power characteristics(e.g., OPT, OPR) associated with an optical link, on a user-specifiedroute, before and after a component (e.g., an FRM) has adjusted thepower of the optical link (e.g., via dynamic spectral equalization, PO,LPO). BCSE 2705 may display the power characteristics for a source node,a destination node, and/or one or more intermediate nodes that connectthe source node to the destination node. BCSE 2705 may show or hide oneor more power characteristics based on user input. Additionally, oralternatively, BCSE 2705 may show or hide information (e.g., powercharacteristics) associated with one or more nodes and/or NEs 250 basedon user input (e.g., user input of a set of optical links associatedwith the nodes).

For example, BCSE 2705 may display OPT and/or OPR for an optical link ona source/destination component (e.g., an “AOFX/SOFX,” an “FMM,” and/oran “FSM”) at a node where the optical link is added or dropped.Additionally, or alternatively, BCSE 2705 may display OPT, OPR, LPO,and/or PO for an optical link on an FRM and/or an FRM port at a nodewhere the optical link is not added or dropped (e.g., where the opticallink is transmitted or expressed). In some implementations, BCSE 2705may display power characteristics at component ingress and egress pointsfor one or more optical links (e.g., every optical link) on a set ofuser-specified nodes.

FIG. 28 is a diagram of an example data structure 2800 that storesinformation associated with an optical network. Data structure 2800 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 2800 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 2800may be displayed by UI 700 (e.g., by BSCE 2705). For example, datastructure 2800 may be represented as a table on UI 700 (e.g., by chartelement 720).

Data structure 2800 may include a collection of fields 2802-2842. Datastructure 2800 includes fields 2802-2842 for explanatory purposes. Inpractice, data structure 2800 may include additional fields, fewerfields, different fields, or differently arranged fields than aredescribed with respect to data structure 2800.

Field 2802 may store information that identifies an optical link (e.g.,a super-channel). For example, field 2802 may identify an optical linkusing a number and/or another identifier (e.g., “1,” “SCH 1,” “6a,”etc.). Information associated with a set of optical links stored by datastructure 2800 may be displayed by UI 700 based on user input (e.g.,user input of an optical route that includes the set of optical links).

Field 2804 may store information that identifies an optical link typeassociated with the optical link identified by field 2802. For example,field 2804 may identify an optical link type using a modulation format(e.g., QPSK) and/or a bandwidth (e.g., 500 GHz) associated with anoptical link.

Field 2806 may store information that identifies a route directionassociated with the optical link identified by field 2802. In thefigures, a route direction may be identified by “W” or “West” for onedirection, or “E” or “East” for another direction. Fields 2808-2842 maybe displayed in a different order depending on the route directionassociated with the optical link identified by field 2802.

Field 2808 may store information that identifies a cross-connect typeassociated with the optical link identified by field 2802 at a sourcenode component (e.g., an FRM, an FMM, an FSM, etc.). A cross-connecttype may be an add/drop cross-connect (“A/D”), which may indicate thatthe optical link is added or dropped at the component. In someimplementations, a cross-connect type may be express (“Exp”), which mayindicate that the optical link is received and/or transmitted at thecomponent, and is not added or dropped.

Field 2810 may store information that identifies a source node componentand/or port that receives, from the source node, the optical linkidentified by field 2802. For example, field 2810 may identify a sourcenode component using a component and/or port identifier (e.g.,“4-A-7-T1”).

Field 2812 may store information that identifies an OPR associated withthe optical link identified by field 2802 when the optical link isreceived by the component identified by field 2810.

Field 2814 may store information that identifies an update date and/ortime associated with the OPR identified by field 2812. For example,field 2814 may identify the last time the OPR identified by field 2812was measured, or the last time a power adjustment associated with theOPR identified by field 2812 was made.

Field 2816 may store information that identifies an LPO associated withthe optical link identified by field 2802 when the optical link isprocessed by the component identified by field 2810 and/or field 2818.

Field 2818 may store information that identifies a source node componentand/or port that transmits, from the source node, the optical linkidentified by field 2802. For example, field 2818 may identify a sourcenode component using a component and/or port identifier (e.g.,“4-A-3-L1-1”).

Field 2820 may store information that identifies a PO associated withthe component identified by field 2818.

Field 2822 may store information that identifies an update date and/ortime associated with the OPT identified by field 2824. For example,field 2822 may identify the last time the OPT identified by field 2824was measured, or the last time a power adjustment associated with theOPT identified by field 2824 was made.

Field 2824 may store information that identifies an OPT associated withthe optical link identified by field 2802 when the optical link istransmitted by the component identified by field 2818.

Field 2826 may store information that identifies a destination nodecomponent and/or port that receives, to the destination node, theoptical link identified by field 2802. For example, field 2826 mayidentify a destination node component using a component and/or portidentifier (e.g., “4-A-3-L1-1”).

Field 2828 may store information that identifies an OPR associated withthe optical link identified by field 2802 when the optical link isreceived by the component identified by field 2826.

Field 2830 may store information that identifies an update date and/ortime associated with the OPR identified by field 2828. For example,field 2830 may identify the last time the OPR identified by field 2828was measured, or the last time a power adjustment associated with theOPR identified by field 2830 was made.

Field 2832 may store information that identifies a cross-connect typeassociated with the outgoing optical link identified by field 2802 at adestination node component (e.g., an FRM, an FMM, an FSM, etc.).

Field 2834 may store information that identifies an LPO associated withthe optical link identified by field 2802 when the optical link isprocessed by the component identified by field 2826 and/or field 2836.

Field 2836 may store information that identifies a destination nodecomponent and/or port that transmits, from the destination node, theoptical link identified by field 2802. For example, field 2836 mayidentify a destination node component using a component and/or portidentifier (e.g., “4-A-7-T1”).

Field 2838 may store information that identifies a PO associated withthe optical link identified by field 2802 when the optical link isprocessed by the component identified by field 2836.

Field 2840 may store information that identifies an update date and/ortime associated with the OPT identified by field 2842. For example,field 2840 may identify the last time the OPT identified by field 2842was measured, or the last time a power adjustment associated with theOPT identified by field 2842 was made.

Field 2842 may store information that identifies an OPT associated withthe optical link identified by field 2802 when the optical link istransmitted by the component identified by field 2836.

FIG. 29 is a diagram of an example element 2900 of a user interface thatdisplays optical network information. Element 2900 may be displayed byUI 700. Element 2700 may include tab element 725, tab element 730, and apath connectivity element 2905. Additionally, or alternatively, element2900 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 29.

Path connectivity element 2905 may be displayed based on user selectionof a tab element 725 and/or a tab element 730 corresponding to pathconnectivity element 2905, and/or based on user input via user inputelement 705. In some implementations, user selection of a tab element725 may cause different tabs to be displayed by tab element 730.

Path connectivity element 2905 may display information associated withan optical route, information associated with NEs 250, and/orinformation associated with optical links. The displayed information maybe based on user input (e.g., user input of an optical route). In someimplementations, path connectivity element 2905 may display a set ofcomponent ports on an optical route associated with a set ofuser-specified optical links.

In some implementations, path connectivity element 2905 may display apath (e.g., physical and/or logical connection or termination points)that an optical link takes along a user-specified route from a sourcenode to a destination node, which may include one or more intermediatenodes that connect the source node and the destination node.

FIG. 30 is a diagram of an example data structure 3000 that storesinformation associated with an optical network. Data structure 3000 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 3000 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 3000may be displayed by UI 700 (e.g., by path connectivity element 2905).For example, data structure 3000 may be represented as a table on UI 700(e.g., by chart element 720).

Data structure 3000 may include a collection of elements 3002-3026. Datastructure 3000 includes elements 3002-3026 for explanatory purposes. Inpractice, data structure 3000 may include additional elements, fewerelements, different elements, or differently arranged elements than aredescribed with respect to data structure 3000. Each element 3002-3026may contain one or more fields.

Element 3002 may include a field that stores information that identifiesa source and/or destination node (e.g., a location where auser-specified optical link is added or dropped). For example, element3002 may identify a node using a number and/or another identifier (e.g.,“Node-1”). Information associated with a set of nodes stored by datastructure 3000 may be displayed by UI 700 based on user input (e.g.,user input of an optical link associated with the set of transmittingnodes).

Element 3004 may include a field that stores information that identifiesa component and/or port associated with the node identified by element3002. In some implementations, element 3004 may include one or morefields that store information that identifies a service state and/or anadministrative state associated with the component and/or portidentified by element 3004. Additionally, or alternatively, element 3004may include one or more fields that store information that identifies aparameter (e.g., PO, LPO, OPT, OPR, etc.) associated with the componentand/or port identified by element 3004. Additionally, or alternatively,element 3004 may include one or more fields that store information thatindicates whether a parameter associated with the component and/or portidentified by element 3004 is automatically being updated. Additionally,or alternatively, element 3004 may include one or more fields that storeinformation that indicates whether the component and/or port identifiedby element 3004 is able to communicate with another component.

Elements 3006-3014 may identify a component and/or port associated withthe node identified by element 3002. For example, element 3006 mayidentify a source/destination component and/or port. Element 3008 mayidentify an FSM/FMM and/or an add/drop port on an FSM/FMM. Element 3010may identify an FSM/FMM and/or a line port on an FSM/FMM.

Element 3012 may identify an FRM and/or an add/drop port associated withan FRM. Element 3014 may identify an FRM and/or a system port associatedwith an FRM.

Elements 3006-3014 may include element 3004. For example, elements3006-3014 may include one or more fields that store information thatidentifies a service state, an administrative state, a parameter,whether a parameter is being automatically updated, and/or acommunication capability, associated with the components identified byelements 3006-3014.

Element 3016 may include a field that stores information that identifiesan express node (e.g., a location where a user-specified optical link isreceived and/or transmitted, but is not added or dropped). For example,element 3016 may identify a node using a number and/or anotheridentifier (e.g., “Node-2”). A set of nodes stored by data structure3000 may be displayed by UI 700 based on user input (e.g., user input ofan optical link associated with the set of transmitting nodes).

Element 3018 may include a field that stores information that identifiesa component and/or port associated with the node identified by element3016. In some implementations, element 3018 may include one or morefields that store information that identifies a service state and/or anadministrative state associated with the component and/or portidentified by element 3018. Additionally, or alternatively, element 3018may include one or more fields that store information that identifies aparameter (e.g., PO, LPO, OPT, OPR, etc.) associated with the componentand/or port identified by element 3018. Additionally, or alternatively,element 3018 may include one or more fields that store information thatindicates whether a parameter associated with the component and/or portidentified by element 3018 is automatically being updated. Additionally,or alternatively, element 3018 may include one or more fields that storeinformation that indicates whether the component and/or port identifiedby element 3018 is able to communicate with another component.

Elements 3020-3026 may identify a component and/or port associated withthe node identified by element 3016. For example, element 3020 mayidentify an FRM and/or an FRM port that receives an optical signal atthe node (e.g., from another node). Element 3022 may identify an FRMand/or an FRM port that transmits the signal at the node (e.g., toanother FRM on the node). Element 3024 may identify an FRM and/or an FRMport that receives the signal at the node (e.g., from another FRM on thenode). Element 3026 may identify an FRM and/or an FRM port thattransmits the signal from the node (e.g., to another node).

Elements 3020-3026 may include element 3018. For example, elements3020-3026 may include one or more fields that store information thatidentifies a service state, an administrative state, a parameter,whether a parameter is being automatically updated, and/or acommunication capability, associated with the components identified byelements 3020-3026.

FIG. 31 is a diagram of an example element 3100 of a user interface thatdisplays optical network information. Element 3100 may be displayed byUI 700. Element 3100 may include tab element 725, tab element 730, andan optical link power chart element 3105. Additionally, oralternatively, element 3100 may include fewer elements, additionalelements, different elements, or differently arranged elements thanthose illustrated in FIG. 31.

Optical link power chart element (“OLPCE”) 3105 may be displayed basedon user selection of a tab element 725 and/or a tab element 730corresponding to OLPCE 3105, and/or based on user input via user inputelement 705. In some implementations, user selection of a tab element725 may cause different tabs to be displayed by tab element 730.

OLPCE 3105 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical route). In some implementations, OLPCE3105 may display information (e.g., a power parameter) associated with aset of nodes that are associated with a user-specified optical link. Thedisplayed information may be associated with a data channel (e.g.,BAND).

For example, OLPCE 3105 may display a graph of information associatedwith one or more nodes. The one or more nodes represented on the graphmay be based on user input (e.g., user input of an optical routeassociated with the nodes via user input element 705). The informationdisplayed on the graph may include a node parameter (e.g., a powerparameter, a gain parameter, OPR, OPT, PO, LPO, PLO, etc.). The order inwhich nodes are displayed on the graph may be based on user input (e.g.,via option element 830). In some implementations, OLPCE 3105 may displaya line graph of OPT and/or OPR for multiple nodes associated with auser-specified route, as illustrated.

FIG. 32 is a diagram of an example element 3200 of a user interface thatdisplays optical network information. Element 3200 may be displayed byUI 700. Element 3200 may include tab element 725, tab element 730, and aband cross-section chart element 3205. Additionally, or alternatively,element 3200 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 32.

Band cross-section chart element (“BCSCE”) 3205 may be displayed basedon user selection of a tab element 725 and/or a tab element 730corresponding to BCSCE 3205, and/or based on user input via user inputelement 705. In some implementations, user selection of a tab element725 may cause different tabs to be displayed by tab element 730.

BCSCE 3205 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical route). In some implementations, BCSCE3205 may display information (e.g., a power parameter) associated with aset of optical links that are associated with a set of user-specifiednodes.

For example, BCSCE 3205 may display a graph of information associatedwith a node. The node represented on the graph may be based on userinput (e.g., user input, via user input element 705, of an optical routeassociated with the node). The information displayed on the graph mayinclude a node parameter (e.g., a power parameter, a gain parameter,OPR, OPT, PO, LPO, PLO, etc.). The order in which nodes are displayed onthe graph may be based on user input (e.g., via option element 830). Insome implementations, BCSCE 3205 may display a bar graph of OPR, OPTand/or PO values for multiple optical links on a node associated with auser-specified route, as illustrated.

FIG. 33 is a diagram of an example element 3300 of a user interface thatdisplays optical network information. Element 3300 may be displayed byUI 700. Element 3300 may include tab element 725, tab element 730, andan OTS power chart element 3305. Additionally, or alternatively, element3300 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 33.

OTS power chart element 3305 may be displayed based on user selection ofa tab element 725 and/or a tab element 730 corresponding to OTS powerchart element 3305, and/or based on user input via user input element705. In some implementations, user selection of a tab element 725 maycause different tabs to be displayed by tab element 730.

OTS power chart element 3305 may display information associated with anoptical route, information associated with NEs 250, and/or informationassociated with optical links. The displayed information may be based onuser input (e.g., user input of an optical route). In someimplementations, OTS power chart element 3305 may display information(e.g., a power parameter) associated with a set of nodes that areassociated with a user-specified optical link. The displayed informationmay be associated with a combined data channel and control channel(e.g., OTS).

For example, OTS power chart element 3305 may display a graph ofinformation associated with one or more nodes. The one or more nodesrepresented on the graph may be based on user input (e.g., user input ofan optical route associated with the nodes via user input element 705).The information displayed on the graph may include a node parameter(e.g., a power parameter, a gain parameter, OPR, OPT, PO, LPO, PLO,etc.). The order in which nodes are displayed on the graph may be basedon user input (e.g., via option element 830). In some implementations,OTS power chart element 3305 may display a line graph of OPT and/or OPRfor multiple nodes associated with a user-specified route, asillustrated.

FIG. 34 is a diagram of an example element 3400 of a user interface thatdisplays optical network information. Element 3400 may be displayed byUI 700. Element 3400 may include tab element 725, tab element 730, and again/loss chart element 3405. Additionally, or alternatively, element3400 may include fewer elements, additional elements, differentelements, or differently arranged elements than those illustrated inFIG. 34.

Gain/loss chart element (“GLCE”) 3405 may be displayed based on userselection of a tab element 725 and/or a tab element 730 corresponding toGLCE 3405, and/or based on user input via user input element 705. Insome implementations, user selection of a tab element 725 may causedifferent tabs to be displayed by tab element 730.

GLCE 3405 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical route). In some implementations, GLCE3405 may display information (e.g., a gain parameter, a span lossparameter, etc.) associated with a set of nodes that are associated witha user-specified optical link.

For example, GLCE 3405 may display a graph of information associatedwith one or more nodes. The one or more nodes represented on the graphmay be based on user input (e.g., user input of an optical routeassociated with the nodes via user input element 705). The informationdisplayed on the graph may include a node parameter (e.g., a powerparameter, a gain parameter, OPR, OPT, PO, LPO, PLO, CG, SL, etc.). Theorder in which nodes are displayed on the graph may be based on userinput (e.g., via option element 830). In some implementations, GLCE 3105may display a line graph of CG and/or SL values for multiple nodesassociated with a user-specified route, as illustrated.

FIG. 35 is a diagram of an example element 3500 of a user interface thatdisplays optical network information. Element 3500 may be displayed byUI 700. Element 3500 may include a channel power table element 3505.Additionally, or alternatively, element 3500 may include fewer elements,additional elements, different elements, or differently arrangedelements than those illustrated in FIG. 35.

Channel power table element (“CPTE”) 3505 may be displayed based on userselection of user input via user input element 705 and/or user selection(e.g., a mouse click) of an element displayed by graphical element 710and/or chart element 720. In some implementations, CPTE 3505 may displayinformation associated with an optical route, information associatedwith NEs 250, and/or information associated with optical links. Thedisplayed information may be based on user input (e.g., user input of anoptical route).

CPTE 3505 may display information associated with an optical route,information associated with NEs 250, and/or information associated withoptical links. The displayed information may be based on user input(e.g., user input of an optical link). In some implementations, CPTE3505 may display information (e.g., channels) associated with an opticallink on a user-specified route. For example, the displayed informationmay be based on user selection of an element displayed by graphicalelement 710 and/or table element 740.

In some implementations, CPTE 3505 may display power characteristics(e.g., OPT, OPR, PO) for one or more optical links included in auser-specified optical link group. The power characteristics may bedisplayed for a user-specified route, which may include a source node, adestination node, and/or one or more intermediate nodes that connect thesource node to the destination node. CPTE 3505 may show or hide one ormore power characteristics based on user input. Additionally, oralternatively, CPTE 3505 may show or hide information (e.g., powercharacteristics) associated with one or more nodes and/or optical linksbased on user input (e.g., user input of a set of optical linksassociated with the nodes).

For example, CPTE 3505 may display OPT and/or OPR for an optical and/oran optical link group on a source node, a destination node, and/or anintermediate node (e.g., in one or both transmission directions).

FIG. 36A is a diagram of an example data structure 3600 that storesinformation associated with an optical network. Data structure 3600 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 3600 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 3600may be displayed by UI 700 (e.g., by CPTE 3505). For example, datastructure 3600 may be represented as a table on UI 700 (e.g., by chartelement 720).

Data structure 3600 may include a collection of fields 3602-3616. Datastructure 3600 includes fields 3602-3616 for explanatory purposes. Inpractice, data structure 3600 may include additional fields, fewerfields, different fields, or differently arranged fields than aredescribed with respect to data structure 3600.

Field 3602 may store information that identifies an optical link (e.g.,a channel). For example, field 3602 may identify an optical link using anumber and/or another identifier (e.g., “1,” “CH 1,” “6a,” etc.).Information associated with a set of optical links stored by datastructure 3600 may be displayed by UI 700 based on user input (e.g.,user input of an optical route associated with the set of opticallinks).

Field 3604 may store information that identifies an optical link group(e.g., a super-channel, a super-channel group, etc.) consisting of oneor more optical links identified by field 3602. For example, field 3604may identify an optical link group using a number and/or anotheridentifier (e.g., “1,” “SCH 1,” “6a,” etc.). In FIG. 36A, data structure3600 may represent a channel group mode of “dual,” where two channelsare grouped together to form a super-channel. Thus, the optical linkgroups identified by field 3604 consist of two optical links identifiedby field 3602.

Field 3606 may store information that identifies a bandwidth associatedwith the optical link group identified by field 3604. For example, abandwidth may be represented in gigahertz (GHz), which may represent anamount of bandwidth allocated to an optical link group for transmissionof an optical signal.

Field 3608 may store information that identifies a wavelength associatedwith the optical link identified by field 3602. For example, eachoptical link (e.g., channel) may be associated with a differentwavelength of light. A wavelength may be represented in nanometers(“nm”).

Field 3610 may store information that identifies a service state of anode associated with the optical link identified by field 3602.

Field 3612 may store information that identifies an OPT and/or an OPRassociated with a node that transmits and/or receives the optical linkidentified by field 3602.

Field 3614 may store information that identifies a Pre-FEC BER and/or aPost-FEC BER associated with the optical link group identified by field3604. In some implementations, multiple optical links may be multiplexedtogether to form an optical link group. Field 3614 may identify aminimum and/or maximum pre-FEC BER associated with one of the opticallinks in the optical link group (e.g., an optical link identified byfield 3602). Similarly, field 3614 may identify a minimum and/or maximumpost-FEC BER associated with one of the optical links in the opticallink group.

Field 3616 may store information that identifies a signal quality (e.g.,“Q-Val”) associated with the optical link identified by field 3602. Asignal quality may include a signal-to-noise ratio, a signalinterference to noise ratio (SINR), and/or another quality parameter. Insome implementations, field 3602 may identify a signal qualityassociated with a single optical link and/or an optical link group.Additionally, or alternatively, field 3616 may identify a minimum and/ormaximum signal quality associated with one of the optical links in theoptical link group.

Fields 3608-3616 may be associated with one or more nodes (e.g., asource node and/or a destination node). In some implementations, UI 700may display the information stored in fields 3608-3616 as beingassociated with a particular node. Additionally, or alternatively, UI700 may display fields 3608-3616 in a different manner (e.g., order)based on user input (e.g., via user input element 705 and/or optionelement 830).

FIG. 36B is a diagram of an example data structure 3600 that storesinformation associated with an optical network. Data structure 3600 maybe stored in a memory device (e.g., RAM, hard disk, etc.) associatedwith one or more devices and/or components shown in FIGS. 2-4. Forexample, data structure 3600 may be stored by NA 220 and/or user device230. In some implementations, information stored by data structure 3600may be displayed by UI 700 (e.g., by CPTE 3505). For example, datastructure 3600 may be represented as a table on UI 700 (e.g., by chartelement 720).

Data structure 3600 may include data structure 3620 and/or datastructure 3630, both of which may include a collection of fields3602-3616, as described herein in connection with FIG. 36A. Datastructure 3600 includes fields 3602-3616 for explanatory purposes. Inpractice, data structure 3600 may include additional fields, fewerfields, different fields, or differently arranged fields than aredescribed with respect to data structure 3600.

Field 3602 may store information that identifies an optical link (e.g.,a channel). For example, field 3602 may identify an optical link using anumber and/or another identifier (e.g., “1,” “CH 1,” “6a,” etc.).Information associated with a set of optical links stored by datastructure 3600 may be displayed by UI 700 based on user input.

Field 3604 may store information that identifies an optical link group(e.g., a super-channel) consisting of one or more optical linksidentified by field 3602. For example, field 3604 may identify anoptical link group using a number and/or another identifier (e.g., “1,”“SCH 1,” “6a,” etc.).

In FIG. 36B, data structure 3620 may represent a channel group mode of“single,” where channels are not grouped together to form super-channels(e.g., each channel is kept separate). Thus, the optical link groupsidentified by field 3604 in data structure 3620 consist of one opticallink identified by field 3602. Data structure 3630 may represent achannel group mode of “all,” where ten channels are grouped together toform a super-channel. Thus, the optical link groups identified by field3604 in data structure 3630 consist of ten optical links identified byfield 3602.

Certain user interfaces have been described with regard to FIGS. 1B, 7,8, 9A-9C, 10A-10B, 11, 12A-12D, 13, 14A-14C, 15-18, 19A-19D, 20A-20B,21A-21B, 22A-22B, 23-35, and 36A-36B. In some implementations, the userinterfaces may be customizable by a device. Additionally, oralternatively, the user interfaces may be pre-configured to a standardconfiguration, a specific configuration based on a type of device onwhich the user interfaces are displayed, or a set of configurationsbased on capabilities and/or specifications associated with a device onwhich the user interfaces are displayed.

Certain data structures have been presented with regard to FIGS. 24-26,28, 30, 36A, and 36B. These data structures are purely examples andmerely serve to facilitate the description of the storage ofinformation.

While the data structures presented with regard to FIGS. 24-26, 28, 30,36A, and 36B are represented as tables with rows and columns, inpractice, the data structures may include any type of data structure,such as a linked list, a tree, a hash table, a database, or any othertype of data structure. The data structures may include informationgenerated by a device and/or component. Additionally, or alternatively,the data structures may include information provided from any othersource, such as information provided by one or more users, and/orinformation automatically provided by one or more other devices.

FIG. 37 is a flow chart of an example process 3700 for exporting sessioninformation to a text file. In some implementations, one or more processblocks of FIG. 37 may be performed by NA 220 and/or user device 230. Insome implementations, one or more process blocks of FIG. 37 may beperformed by another device or a group of devices separate from orincluding NA 220 and/or user device 230, such as NPS 210 and/or NE 250.

As shown in FIG. 37, process 3700 may include receiving a request toexport session information for a UI session (block 3710). For example,UI manager 420 (e.g., included in NA 220 and/or user device 230) mayreceive a request to export session information.

A UI session may allow a user to interact with network information via aUI (e.g., the UI provided at block 630 and/or block 650 of FIG. 6). Aspreviously discussed, network information may include quantities,locations, capacities, parameters, and/or configurations of NEs 250;characteristics and/or configurations (e.g., capacities) of opticallinks between NEs 250; traffic demands of NEs 250 and/or optical linksbetween NEs 250, and/or any other network information associated withoptical network 240 (e.g., optical device configurations, digital deviceconfigurations, etc.).

In some implementations, UI manager 420 may cause network information tobe displayed, allow a user to model optical network 240, and/or allow auser to plan changes to optical network 240 during a UI session. Forexample, the user may provide inputs to NA 220 and/or user device 230 tonavigate through various views of the network information available viathe UI (e.g., as shown in FIGS. 7, 8, 9A-9C, 10A-10B, 11, 12A-12D, 13,14A-14C, 15-18, 19A-19D, 20A-20B, 21A-21B, 22A-22B, 23-35, and 36A-36B).Moreover, the user may input user-specified changes (e.g., a userspecified parameter) for NE(s) 250 via the UI as discussed at block 670in FIG. 6. Furthermore, the user may input a note or other text to bedisplayed in the UI. For example, the user may input a note about aparticular NE 250 and/or optical link that the user or another user mayreference at a later time via the UI.

In some implementations, a user may input a request via the UI to exportsession information. The session information may include sessionidentification information that identifies the session and/or networkinformation used to generate the UI for the UI session. Additionally, oralternatively, the session information may indicate a log of user inputsand/or user interactions with the UI, the user specified changes inputvia the UI, and/or notes input by the user. In other words, the sessioninformation may include information used to reconstruct the UI usedduring the UI session.

In some implementations, the user may input a request that sessioninformation for a particular optical route be exported. Additionally, oralternatively, the user may input a request that session information formultiple optical routes be exported.

As further shown in FIG. 37, process 3700 may include exporting thesession information to a text file (block 3720). For example, UI manager420 (e.g., included in NA 220 and/or user device 230) may export thesession information based on the request.

UI manager 420 may export the session information by creating a textfile including the session information in a text format. The sessioninformation may be stored in particular manner within the text file sothat particular session information may be referenced when reading thetext file. For example, particular text identifiers may be used toidentify particular network information (e.g., a particular NE 250,optical link, optical channel; etc.; a particular type of NE 250,optical link, optical channel, etc.; a property of NE 250, an opticallink, an optical channel, etc.) and/or particular session informationmay be arranged within the text file in a particular manner that may bereferenced when read by a device.

The text file may include a TSV file, character-separated values (CSV)file, a delimiter-separated values (DSV) file, and/or another flat textfile. The session information included in the text file may be for oneor more optical routes. The session information included in the textfile may be in a human readable format. UI manager 420 may store thetext file in a user specified location within a memory included in oraccessible to NA 220 and/or user device 230.

Although FIG. 37 shows example blocks of process 3700, in someimplementations, process 3700 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 37. Additionally, or alternatively, two or more of theblocks of process 3700 may be performed in parallel.

FIG. 38 is a diagram of an example implementation 3800 relating toexample process 3700 shown in FIG. 37. FIG. 38 shows an example ofexporting session information to a text file.

In FIG. 38, assume a user has started a UI session for viewing networkinformation for optical network 240.

As shown in FIG. 38, user device 230 may display a window 3810 includinga UI during the UI session. A user may use a cursor to input a requestto export session information via the UI. For example, the user mayclick an “Export” button. Based on inputting the request, user device230 may display a window 3820 that allows the user to select a file namefor a text file and a location for the text file to be saved. The usermay use the cursor to select “Save.” Based on selecting “Save,” userdevice 230 may export session information by saving the text file thatincludes the session information. User device 230 may display a window3830 indicating that the session information has been successfullyexported to a text file.

As indicated above, FIG. 38 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 38.

FIG. 39 is a diagram of an example implementation 3900 relating toexample process 3700 shown in FIG. 37. FIG. 39 shows an example of atext file that includes session information.

As shown in FIG. 39, the session information included in the text filemay be in a human readable text format. The session information mayinclude session identification information 3910 and network information3920. As shown in FIG. 39, the text (e.g., the session information) maybe arranged in a particular arrangement and with particular identifiersthat UI manager 420 may use to identify the session information includedin the text file.

As indicated above, FIG. 39 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 39.

FIG. 40 is a flow chart of an example process 4000 for reconstructing aUI session based on a text file. In some implementations, one or moreprocess blocks of FIG. 40 may be performed by NA 220 and/or user device230. In some implementations, one or more process blocks of FIG. 40 maybe performed by another device or a group of devices separate from orincluding NA 220 and/or user device 230, such as NPS 210 and/or NE 250.

As shown in FIG. 40, process 4000 may include receiving a text fileincluding session information (block 4010). For example, NA 220 and/oruser device 230 may receive the text file.

In some implementations, the NA 220 and/or the user device 230 thatexported the session information to a text file (e.g., at block 3720 inFIG. 37) may send the text file to another NA 220 and/or user device230. The other NA 220 and/or user device 230 may receive the text file(e.g., via a network). Additionally, or alternatively, NA 220 and/oruser device 230 may receive the text file in an offline manner (e.g.,via a memory stick).

In this way, NA 220 and/or user device 230 may receive networkinformation, included within the session information of the text file,without having access to NEs 250 and/or optical network 240.

As further shown in FIG. 40, process 4000 may include reconstructing theUI session based on the text file (block 4020). For example, UI manager420 (e.g., included in NA 220 and/or user device 230) may reconstructthe UI session based on the text file.

In some implementations, the text file may include network informationfor multiple optical routes. In some implementations, UI manager 420 mayreconstruct the multiple optical routes in the UI session.Alternatively, UI manager 420 may prompt a user, via a UI, to select anoptical route to be reconstructed in the UI session. The user may inputa selection of an optical route via the UI, and UI manager 420 mayreceive the selection. UI manager 420 may reconstruct the optical routein the UI session based on the selection.

UI manager 420 may read the text (e.g., the session information)included in the text file and reconstruct the UI session based on thetext. For example, in addition to, or alternatively from, using storednetwork information (e.g., like at block 630 in FIG. 6) or using networkinformation received from NEs 250 (e.g., like at block 640 in FIG. 6),UI manager 420 may construct a UI session for display of networkinformation via a UI based on the text of the text file.

The session information included in the text file may be stored inparticular manner so that particular session information may beidentified when UI manager 420 reads the text file. For example,particular text identifiers may be used to identify particular networkinformation (e.g., a particular NE 250, optical link, optical channel;etc.; a particular type of NE 250, optical link, optical channel, etc.;a property of NE 250, an optical link, an optical channel, etc.) and/orparticular session information may be arranged within the text file in aparticular manner that may be referenced when read by a device.Accordingly, UI manager 420 may determine the session informationrepresented by the text in the text file based on text identifiersand/or an arrangement of the text within the text file. UI manager 420may reconstruct the UI session based on the determined sessioninformation from the text file.

The reconstructed UI session based on the text file may have the samefunctionalities as a UI session constructed based on the networkinformation received from NEs 250. For example, the reconstructed UI maycause network information to be displayed via the UI, allow a user tomodel optical network 240 via the UI, and/or allow a user to planchanges to optical network 240. For instance, the reconstructed UI mayinclude graphical representations of NEs 250, optical links, opticalroutes, and/or other parts of optical network 240. Additionally, oralternatively, the user may provide inputs to NA 220 and/or user device230 to navigate through various views or elements of the networkinformation available via the UI (e.g., as shown in FIGS. 7, 8, 9A-9C,10A-10B, 11, 12A-12D, 13, 14A-14C, 15-18, 19A-19D, 20A-20B, 21A-21B,22A-22B, 23-35, and 36A-36B). For example, the reconstructed UI maypermit a user to navigate through the network information in the samemanner as the UI manager 420, included in NA 220 and/or user device 230that exported the text file, permitted a user to navigate through thenetwork information.

Additionally, or alternatively, the UI session reconstructed based onthe text file may provide a UI with the same available view types as aUI generated based on network information received from NEs 250. Forexample, the view types may include a data channel view, a controlchannel view, an optical link termination view, or a combination ofthese view types as previously discussed. Additionally, oralternatively, the view types may include a super channel view thattraces a super channel through the optical network and/or a filters aquantity of super channels displayed in the UI. Furthermore, the viewtypes may include a summary view that summarizes the network informationfor the entire optical network 240 or a part of optical network 240. Forexample, the summary view may summarize the network information forparticular NEs 250, optical links, optical channels, etc. included inoptical network 240.

As further shown in FIG. 40, process 4000 may include providing the UIsession for display in the UI (block 4030). For example, UI manager 420may provide the UI session for display in the UI.

UI manager 420 may provide the UI session for display by providing thesession information for display via the UI. For example, networkinformation for optical network 240 may be displayed, user-specifiedchanges for NE(s) 250 made via the UI session on the NA 220 and/or userdevice 230 that exported the text file may be displayed, and/or a noteor other text input by a user of the NA 220 and/or user device 230 thatexported the text file may be displayed. Additionally, or alternatively,the reconstructed UI may include graphical representations of NEs 250,optical links, optical routes, and/or other parts of optical network 240(e.g., as shown in FIGS. 7, 8, 9A-9C, 10A-10B, 11, 12A-12D, 13, 14A-14C,15-18, 19A-19D, 20A-20B, 21A-21B, 22A-22B, 23-35, and 36A-36B).

A user may use the reconstructed UI session to model optical network240, and/or plan changes to optical network 240. For example, the usermay provide inputs to NA 220 and/or user device 230 to navigate throughvarious views of the network information available via the UI (e.g., asshown in FIGS. 7, 8, 9A-9C, 10A-10B, 11, 12A-12D, 13, 14A-14C, 15-18,19A-19D, 20A-20B, 21A-21B, 22A-22B, 23-35, and 36A-36B). Moreover, theuser may input user-specified changes (e.g., a user specified parameter)and simulate how the changes may change optical network 240. However, insome implementations, the user-specified changes may not be actually beprovided to optical network 240 (e.g., NEs 250) because NA 220 and/oruser device 230 that reconstructs the UI session may not have access to,and may not be permitted to communicate with, optical network 240 and/orNEs 250. Thus, the reconstructed UI session may be used for planningpurposes and changes to optical network 240 may be made at a later timeif and when access to optical network 240 is permitted.

Thus, the NA 220 and/or user device 230 that reconstructs the UI sessionmay reconstruct the UI session without having to monitor optical network240. Accordingly, additional devices (e.g., servers) used to monitoroptical network 240 do not need to be provided to test and/or manageoptical network 240. Moreover, optical network 240 may be kept privateand secure by not allowing access to optical network 240 by a NA 220and/or a user device 230 tasked with improving and/or changing opticalnetwork 240, while still allowing the NA 220 and/or user device 230 toplan changes and/or manage optical network 240.

Furthermore, development, enhancements, and testing of the UI may beeasier when the UI is constructed or populated with network informationfrom a text file than when the UI is constructed or populated withnetwork information gathered from NEs 250. For example, changes to theUI (e.g., changes in a manner in which network information is presented)may be tested offline when the network information is gathered from atext file, as opposed to testing the UI online by obtaining the networkinformation from NEs 250 via a network.

Although FIG. 40 shows example blocks of process 4000, in someimplementations, process 4000 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 40. Additionally, or alternatively, two or more of theblocks of process 4000 may be performed in parallel.

FIG. 41 is a diagram of an example implementation 4100 relating toexample process 4000 shown in FIG. 40. FIG. 41 shows an example ofreconstructing a UI session based on a text file.

In FIG. 41, assume user device 230 displays a window 4110 that prompts auser to select an application to execute. As shown in FIG. 41, the usermay use a cursor to select a link viewer application (e.g., “launchDLV”)that provides a UI for interacting with network information for opticalnetwork 240. User device 230 may execute the link viewer applicationbased on the selection.

As further shown in FIG. 41, user device 230 may display a window 4120based on executing the link viewer application. Window 4120 may promptthe user to select a text file from which to reconstruct a UI session.The user may use the cursor to select a text file.

As further shown in FIG. 41, user device 230 may reconstruct the UIsession based on the text file and display a UI for the reconstructed UIsession in a window 4130. The user may interact with the UI and navigatethrough network information for an optical route included in opticalnetwork 240.

As indicated above, FIG. 41 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 41.

FIG. 42 is a diagram of an example implementation 4200 relating toexample process 4000 shown in FIG. 40. FIG. 42 shows an example ofreconstructing a UI session based on a text file.

In FIG. 42, assume user device 230 displays a window 4210 that prompts auser to select an application to execute. As shown in FIG. 42, the usermay use a cursor to select a link viewer application (e.g., “launchDLV”)that provides a UI for interacting with network information for opticalnetwork 240. User device 230 may execute the link viewer applicationbased on the selection.

As further shown in FIG. 42, user device 230 may display a window 4220based on executing the link viewer application. Window 4220 may promptthe user to select a text file from which to reconstruct a UI session.The user may use the cursor to select a text file. Assume sessioninformation included in the text file includes network information formultiple optical routes included in optical network 240.

As further shown in FIG. 42, user device 230 may display a window 4230based on selecting the text file. Window 4230 may include a list ofoptical routes that have network information included in the text file.The user may use the cursor to select one or more of the optical routes.

As further shown in FIG. 42, user device 230 may reconstruct the UIsession based on the text file and display a UI for the reconstructed UIsession in a window 4240. The user may interact with the UI and navigatethrough network information for the selected optical route(s).

As indicated above, FIG. 42 is provided merely as an example. Otherexamples are possible and may differ from what was described with regardto FIG. 42.

Implementations described herein may export session information, for auser interface session used to display optical network information, to atext file and permit reconstruction of the user interface session basedon the text file. Thus, a user may obtain and view aggregated opticalnetwork information, such as network information associated with networkentities and optical links between the network entities, without havingaccess to the optical network.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, and/or a combination of hardware and software.

Certain user interfaces have been described herein and/or shown in thefigures. A user interface may include a graphical user interface, anon-graphical user interface, a text-based user interface, etc. A userinterface may provide information for display. In some implementations,a user may interact with the information, such as by providing input viaan input component of a device that provides the user interface fordisplay. In some implementations, a user interface may be configurableby a device and/or a user (e.g., a user may change the size of the userinterface, information provided via the user interface, a position ofinformation provided via the user interface, etc.). Additionally, oralternatively, a user interface may be pre-configured to a standardconfiguration, a specific configuration based on a type of device onwhich the user interface is displayed, and/or a set of configurationsbased on capabilities and/or specifications associated with a device onwhich the user interface is displayed.

It will be apparent that systems and/or methods, described herein, maybe implemented in different forms of hardware, firmware, or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods were described herein without reference tospecific software code—it being understood that software and hardwarecan be designed to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one claim, thedisclosure of possible implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items,and may be used interchangeably with “one or more.” Where only one itemis intended, the term “one” or similar language is used. Also, as usedherein, the terms “has,” “have,” “having,” or the like are intended tobe open-ended terms. Further, the phrase “based on” is intended to mean“based, at least in part, on” unless explicitly stated otherwise.

What is claimed is:
 1. A device, comprising: one or more processors to:receive a text file including network information for an opticalnetwork, the network information including information for an opticalroute in the optical network; generate a user interface based on thetext file, the user interface displaying a representation of the opticalroute; provide the user interface for display; receive a user input viathe user interface; change the representation of the optical routedisplayed by the user interface based on the user input and the networkinformation included in the text file to designate another optical routein the optical network; transmit optical signals along said anotherroute in the optical network; display, on the user interface, amodulation format, a bit error rate associated with the optical signalsand a quantity of spectral slices included in an optical link that ispart of the optical route, each of the spectral slices representing aspectrum of a particular size in a frequency band; and display, on theuser interface, a representation of a node connected along the opticalroute and information that identifies an address parameter of an opticalsupervisory channel associated with the node, the address parameterincluding an internet protocol (“IP”) address and a subnet mask address.2. The device of claim 1, where the text file is a tab separated valuesfile or a character-separated values file.
 3. The device of claim 1,where the optical route includes an optical path comprising networkdevices and optical links, and where the representation of the opticalroute displayed by the user interface represents the optical pathcomprising the network devices and the optical links.
 4. The device ofclaim 3, where the one or more processors, when changing therepresentation of the optical route, are further to: cause a differentdisplay of the optical path, comprising the network devices and theoptical links, than displayed before the user input is received.
 5. Thedevice of claim 1, where the one or more processors, when receiving thetext file, are further to: receive the text file without communicatingwith the optical network.
 6. The device of claim 1, where the text fileoriginated from another device that exported the network information tothe text file while executing a user interface session.
 7. The device ofclaim 6, where the one or more processors, when generating the userinterface, are further to: reconstruct the user interface session, thatwas executed by the other saki another device, based on the text file.8. A computer-readable medium storing instructions, the instructionscomprising: one or more instructions that, when executed by one or moreprocessors, cause the one or more processors to: receive a text fileincluding network information for an optical network, the networkinformation including information for an optical route in the opticalnetwork; generate a user interface based on the text file, the userinterface displaying multiple representations of the optical route;provide the user interface for display; receive a user input via theuser interface; change between the multiple representations of theoptical route displayed by the user interface based on the user inputand the network information included in the text file to designateanother optical route in the optical network; transmit optical signalsalong said another route in the optical network; display a modulationformat, a bit error rate associated with the optical signal on the userinterface, and a quantity of spectral slices included in an optical linkthat is part of the optical route, each of the spectral slicesrepresenting a spectrum of a particular size in a frequency band; anddisplay, on the user interface, a representation of a node connectedalong the optical route and information that identifies an addressparameter of an optical supervisory channel associated with the node,the address parameter including an internet protocol (“IP”) address anda subnet mask address.
 9. The computer-readable medium of claim 8, wherethe network information includes information for a plurality of opticalroutes, the plurality of optical routes including the optical route,where the one or more instructions, when executed by the one or moreprocessors, further cause the one or more processors to: present opticalroute information indicating the plurality of optical routes; receive auser selection of the optical route from among the plurality of opticalroutes; and where the one or more instructions, that cause the one ormore processors to generate the user interface, are further to: generatethe user interface based on the user selection.
 10. Thecomputer-readable medium of claim 8, where the text file originated froma device that exported the network information to the text file during auser interface session.
 11. The computer-readable medium of claim 10,where the text file includes user input information that was input intothe device during the user interface session, and where the userinterface displays the user input information, which was input duringthe user interface session on the device that exported the networkinformation to the text file.
 12. The computer-readable medium of claim10, where the one or more instructions, that cause the one or moreprocessors to provide the user interface for display, further cause theone or more processors to: provide a same navigation capability of thenetwork information as provided by the device during the user interfacesession.
 13. The computer-readable medium of claim 8, where the one ormore instructions, when changing between the multiple representations ofthe optical route, further cause the one or more processors to: changebetween different view types of the network information for the opticalroute.
 14. The computer-readable medium of claim 13, where the viewtypes include a control channel view for displaying informationregarding a control channel in the optical network, an optical link viewfor displaying information regarding an optical link in the opticalnetwork, a data channel view for displaying information regarding a datachannel in the optical network, a super channel view for displayinginformation regarding a super channel in the optical network, and asummary view for displaying information regarding a summary of thenetwork information.
 15. A method, comprising: receiving, by a device, atext file including network information for an optical network,generating, by the device, a user interface based on the text file, theuser interface including a plurality of view types for viewing differentrepresentations of the optical network; providing, by the device, theuser interface for display; receiving, by the device, a user input viathe user interface; selecting, by the device, a view type included inthe plurality of view types based on the user input; providing, by thedevice, a representation of the optical network for display based on theselected view type and the network information included in the textfile, the different representations including the representation;transmitting optical signals along an optical route included in theoptical network and shown in the representation; displaying a modulationformat, a bit error rate associated with the optical signals on the userinterface, and a quantity of spectral slices included in an optical linkthat is part of the optical route, each of the spectral slicesrepresenting a spectrum of a particular size in a frequency band; anddisplaying, on the user interface, a representation of a node connectedalong the optical route and information that identifies an addressparameter of an optical supervisory channel associated with the node,the address parameter including an internet protocol (“IP”) address anda subnet mask address.
 16. The method of claim 15, where the view typesinclude a control channel view for displaying information regarding acontrol channel in the optical network, an optical link view fordisplaying information regarding an optical link in the optical network,a data channel view for displaying information regarding a data channelin the optical network, a super channel view for displaying informationregarding a super channel in the optical network, and a summary view fordisplaying information regarding a summary of the network information.17. The method of claim 15, where the text file is a tab separatedvalues file, a character-separated values file, or a delimiter-separatedvalues file.
 18. The method of claim 15, where the text file is a firsttext file, the method further comprising: exporting the networkinformation to a second text file, where the first text file is separatefrom the second text file.
 19. The method of claim 15, where the networkinformation included in the text file is in a human readable format. 20.The method of claim 15, where generating the user interface furthercomprises: reconstructing a user interface session from another device.